agent-passport-system-mcp

Create Action Intent

create_intent

Declare an agent's intended action as the first signed step in a three-signature authorization chain, linking action, target, scope, and delegation before execution.

Instructions

Declare an intent to perform an action. First step of the 3-signature chain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action_type": "<action_type>",
      "target": "<target>",
      "scope_required": "<scope_required>",
      "delegation_id": "<delegation_id>"
    },
    "name": "create_intent"
  }
}

Input Schema

Name	Required	Description
`target`	Yes	What the action operates on
`context`	No	Why the agent wants to do this
`action_type`	Yes	What type of action (e.g. 'web_search', 'commerce:checkout')
`spend_amount`	No	Expected spend amount
`delegation_id`	Yes	Delegation ID authorizing this action
`scope_required`	Yes	Which delegation scope is needed
`spend_currency`	No	Spend currency (e.g. 'usd')

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv4.0.0Aug 1, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Addedv2.8.0May 1, 2026

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds genuine workflow context by disclosing that this is the first of a chain of three signatures, which annotations cannot express. It still omits what state is created, whether the intent expires, and whether abandoning the chain has consequences.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler or repetition. The size is appropriate for the message, though the brevity is partly under-specification rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent write tool in a multi-step signature chain with no output schema, the description should explain what is produced (an intent identifier?) and how it feeds the remaining two steps. Neither the chain's other steps nor the return value are described, leaving the agent unable to complete the workflow from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 7 parameters (including the required action_type, target, scope_required, and delegation_id) are already documented in the schema. The description adds no parameter-level meaning, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Declare an intent to perform an action') and adds positional context ('First step of the 3-signature chain'). However, it never names the other steps or the sibling tools that follow (evaluate_intent, complete_action), so an agent must infer the sequence from the sibling list rather than the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'First step of the 3-signature chain' implies this must be called before the later steps, which is real sequencing guidance. But there are no explicit when/when-not statements, no mention of the prerequisite delegation (implied only by the required delegation_id parameter), and no naming of alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server