agent-passport-system-mcp

Define Emergency Pathway

define_emergency_pathway

Defines a pre-authorized emergency pathway during delegation, letting only the delegator set trigger conditions, expanded scope categories, review authority, and validity for emergency approvals.

Instructions

Define a pre-authorized emergency pathway at delegation time. Only the delegator can define these.

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": {
      "delegation_ref": "<delegation_ref>",
      "description": "<description>",
      "trigger_field": "<trigger_field>",
      "trigger_operator": "<trigger_operator>",
      "trigger_value": "<trigger_value>",
      "expanded_scope_categories": "<expanded_scope_categories>",
      "review_authority": "<review_authority>",
      "valid_until": "<valid_until>"
    },
    "name": "define_emergency_pathway"
  }
}

Input Schema

Name	Required	Default
`description`	Yes
`trust_epoch`	No
`valid_until`	Yes
`max_duration`	No	PT1H
`trigger_field`	Yes
`trigger_value`	Yes
`delegation_ref`	Yes
`review_deadline`	No	PT24H
`review_authority`	Yes
`trigger_operator`	Yes
`expanded_scope_categories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv5.0.2Sep 1, 2026

removedInput schema / properties / trigger_value / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]

addedInput schema / properties / trigger_value / type

Added value: +[
+  "string",
+  "number",
+  "boolean"
+]

Changed4 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
```

addedInput schema / properties / trigger_value / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / trigger_value / type

Removed value: -[
-  "string",
-  "number",
-  "boolean"
-]

Addedv2.8.0May 1, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so the mutation/safety profile is already covered. The description adds genuinely useful context by stating the authorization constraint (only the delegator can define), but says nothing about the effect of the pathway, idempotency, or lifecycle beyond annotations.

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 front-loaded sentences with no wasted words; the core action leads. It is well-structured and tight, though arguably too thin given the underlying complexity.

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 an 11-parameter, 8-required mutation tool with no output schema and no annotation-rich profile, the description is far too sparse. It omits parameter meaning, trigger semantics, and pathway effects, leaving an agent unable to call it correctly without guessing.

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

Parameters1/5

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

The tool has 11 parameters (8 required) with 0% schema description coverage, and the description explains none of them. Critical fields like trigger_field, trigger_operator, trigger_value, expanded_scope_categories, review_authority, and valid_until are left entirely undocumented in both description and schema.

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?

The description names a specific verb ("Define") and resource ("emergency pathway") and adds the timing constraint ("at delegation time"), so an agent can tell what operation is performed. However, it offers no differentiation from related siblings such as activate_emergency or create_delegation, leaving the boundary ambiguous.

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?

"At delegation time" implies a temporal context for when to use it, and "Only the delegator can define these" states an access prerequisite. But there is no explicit when-to-use/when-not or named alternative (e.g., vs activate_emergency), so the usage guidance remains implied rather than stated.

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

Deploy Server