agent-passport-system-mcp

Gateway Process Tool Call (Deprecated)

gateway_process_tool_call

Read-onlyIdempotent

Process a tool call through the gateway enforcement boundary to enforce agent identity, required scope, and spend policy. Deprecated in v3.0.0; use the gateway.aeoess.com REST API.

Instructions

[deprecated in v3.0.0, use the gateway.aeoess.com REST API] Process a tool call through the gateway enforcement boundary.

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": {
      "agentId": "<agentId>",
      "tool": "<tool>",
      "scopeRequired": "<scopeRequired>"
    },
    "name": "gateway_process_tool_call"
  }
}

Input Schema

Name	Required	Description	Default
`tool`	Yes
`params`	No
`agentId`	Yes
`context`	No
`spendAmount`	No
`scopeRequired`	Yes
`spendCurrency`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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 / params / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

Addedv2.8.0May 1, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. But the description adds nothing beyond that: it never explains what 'enforcement boundary' processing entails, whether the underlying tool is actually executed or merely authorized, or how spend/scope failures surface. For a 7-parameter governance tool, that is a large gap.

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 clauses with the deprecation notice correctly front-loaded, so an agent immediately sees the tool is obsolete. Efficient and waste-free, though it spends its one sentence on almost no substantive detail.

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?

Seven undocumented parameters, a nested object, no output schema, and no annotations describing returns leave an agent unable to call this correctly from the description alone. The deprecation notice softens the impact — there is less reason to invest detail in a deprecated tool — but the definition is still under-specified for what it does.

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 coverage is 0% across 7 parameters including a nested free-form 'params' object, and the description supplies no semantics for agentId, tool, scopeRequired, spendAmount, spendCurrency, or context. It neither compensates for the coverage gap nor hints at which fields drive enforcement decisions. Complete omission.

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

Purpose3/5

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

The description names a verb ('process') and resource ('a tool call') and adds the framing 'through the gateway enforcement boundary', so it is slightly more than a restatement of the name. However, it does not distinguish this tool from nearby siblings such as gateway_approve, execute_with_context, or evaluate_intent, and 'process' remains vague about what the gateway actually does (validate, approve, execute?). Minimum viable.

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

Usage Guidelines4/5

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

The deprecation banner is real, actionable guidance: it tells the agent not to use this tool and points at a specific alternative (the gateway.aeoess.com REST API). That is a clear routing instruction, though it gives no condition for when legacy use might still be warranted and no guidance relative to sibling gateway tools.

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

Deploy Server