Skip to content

Discover.

How agents find the right Decision for the job.

You choose which Decisions your agents can see. An agent searches for the judgement it needs, reads what the Decision asks for and calls it.

An agent working through a task often reaches a question your organisation already has rules for, such as whether a refund is due. Discover lets it find the Decision your team built for that judgement and call it, instead of working out an answer of its own.

Only Decisions a person has offered can be found, and every search is recorded with the calls it led to.

Who
Agents in Claude Code, Codex or any MCP client
Where
The TypeFuse MCP server, with three tools
You end up with
Agents using your Decisions for the judgements they cover

Offer it when it’s ready.

A Decision stays private to your team until a person offers it. Its summary tells agents what it’s for and when to use it, in words a person wrote and checked.

  • Off by default, for every new Decision, unless your organisation chooses otherwise
  • A purpose and “when to use” are required before it can be offered; the assistant can suggest both
  • Plain words only. Text that reads like an instruction to an agent is refused

Read the contract.

Before its first call, an agent can read exactly what the Decision needs and what it answers, from the live release.

  • The inputs it needs, straight from the Definition’s state_schema
  • The answers it gives, in TypeSafe’s native shape
  • Which release is live, so the agent knows what it’s calling

Find once, call many.

An agent searches once for each kind of judgement, then calls the Decision for every item. When a job becomes routine, it moves into your code with the Decision bound by name.

  • One search, many calls, each with its own sealed record
  • Remembered across sessions when you add the name to your agent’s instructions
  • Moves into code when the job is routine: your app calls the Decision by name, with no search
Soon: not available yet

See what agents looked for.

Every search is recorded with the calls it led to, so you can see which Decisions agents rely on and which judgements they couldn’t find.

  • Searches, matches and calls, linked from one to the next
  • Searches with no match, grouped, as a list of Decisions you might add
  • Private by default: the words of a search are kept only if you choose

Where it happens.

In the app

  • Write the purpose and when to use it, or let the assistant suggest them
  • Turn “Offered to agents” on for each Decision
  • See searches and the calls they led toSoon: not available yet

Your agent, over MCP

  • search_decisions finds Decisions for a judgement
  • describe_decision returns what one asks for and answers
  • call_decision asks it, and the answer is recorded

Your code

  • A routine job binds the Decision by name with the SDK
  • No search at run time: runtime.decide("acme/refunds", …)
  • Same record, same release rules
The three tools
ToolWhat it doesChanges anything?
search_decisionsFinds offered, deployed Decisions for a judgement, each with the exact call to makeNo
describe_decisionReturns one Decision’s purpose, input, answers and live releaseNo
call_decisionAsks the Decision; returns its answers, the release and the record’s idRecords a call

A Decision that isn’t offered, or isn’t deployed where the agent may call, is refused by name and never swapped for another. The call checks again even if the search was a moment ago.

Private preview

Own your next decision.

Keep the judgement calls your agents and apps make under your control, with a record of every answer.

  • Your criteriaThe people who own a decision set its rules, and change them when the business changes.The people who own a decision set its rules.
  • Your evidenceEvery release is tested against real cases before your application ever sees it.Every release is tested on real cases first.
  • Your recordEvery answer is traced and sealed, ready for an auditor or the customer who asks why.Every answer is traced and sealed.