Escalate a known or unknown blocker; ME classifies and routes the required intervention.
| Name | Required | Description | Default |
|---|---|---|---|
| rights | No | ||
| privacy | No | ||
| deadline | Yes | ||
| agent_key | Yes | ||
| objective | Yes | ||
| blocker_type | No | ||
| idempotency_key | Yes | ||
| max_spend_cents | Yes | ||
| organization_id | Yes | ||
| required_actions | No | ||
| context_reference | No | ||
| forbidden_actions | No | ||
| reliability_target | No | ||
| blocker_description | Yes | ||
| operating_mandate_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It reveals that ME classifies and routes, but does not disclose side effects, required permissions, or the escalation workflow.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, concise but overly terse, omitting essential context while not being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of the schema (15 params, nested objects) and lack of output schema, the description is grossly incomplete. It does not explain the domain context or expected outcomes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 15 parameters with zero coverage. The description does not explain any parameter meanings, relationships, or required formats, leaving agents to guess.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states the action 'escalate' and the object 'blocker', and mentions classification and routing. It is clear enough to distinguish from 'resolve' but lacks specifics on what constitutes a blocker or intervention.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'me_resolve' or 'me_status'. Does not specify conditions for escalation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.