Skip to main content
Glama
aeoess

agent-passport-system-mcp

by aeoess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

define_emergency_pathway

Create a pre-authorized emergency pathway at delegation time by defining trigger conditions, expanded scope categories, review authority, and expiration, so agents can act under vetted urgency.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYes
trust_epochNo
valid_untilYes
max_durationNoPT1H
trigger_fieldYes
trigger_valueYes
delegation_refYes
review_deadlineNoPT24H
review_authorityYes
trigger_operatorYes
expanded_scope_categoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.2
    • 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"
+]
  2. Changed4 schema fields changedv4.0.0
    • 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"
-]
  3. Addedv2.8.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does convey that this is a pre-authorization action available only to the delegator, but it does not explain side effects, persistence, activation behavior, expiration, revocation, or consequences for the underlying delegation. This is thin for an administrative tool with 11 parameters.

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?

The description is two short sentences with no filler. It front-loads the key purpose and includes a useful authorization constraint, making it concise and readable. It loses a point only because it omits vital details while staying brief.

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

Completeness1/5

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

Given 11 parameters, 0% schema coverage, no output schema, and many related sibling tools, this two-sentence description is severely incomplete. An agent would not know what the trigger fields mean, what review_authority and valid_until do, what the tool returns, or how the pathway interacts with delegate, activation, or governance workflows.

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?

Schema description coverage is 0%, and the description adds no explanation for any of the 11 parameters or how they relate to the emergency pathway. Parameter names like trigger_field and expanded_scope_categories hint at meaning, but the description itself provides no semantic guidance.

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 clearly identifies the action ('define'), the resource ('pre-authorized emergency pathway'), and an important timing context ('at delegation time'). It implicitly distinguishes itself from the sibling 'activate_emergency' by focusing on definition rather than activation, but does not explicitly name any alternative.

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?

The phrase 'at delegation time' provides a clear temporal context, and 'Only the delegator can define these' gives an authorization constraint. However, there is no explicit guidance on when to use this tool versus related delegation or emergency tools, and no mention of when not to use it.

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

Deploy Server

Other Tools