Skip to main content
Glama
Sign In
agent-passport-system-mcp

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Commerce Preflight (Moved to Gateway)

commerce_preflight
Read-onlyIdempotent

Returns a machine-readable deprecation notice for the moved 6-gate purchase preflight, directing callers to the gateway commerce endpoint; use SDK predicates or gateway instead.

Instructions

[moved to gateway in SDK 3.3.0] The 6-gate commerce preflight orchestration moved out of the SDK and MCP into the AEOESS gateway. This tool no longer runs the pipeline locally. It returns a machine-readable deprecation notice pointing to the gateway commerce endpoint. Compose the pure gate predicates from the SDK yourself, or call the gateway.

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": {
      "merchant_name": "<merchant_name>",
      "amount": "<amount>",
      "delegation_id": "<delegation_id>",
      "agent_id": "<agent_id>"
    },
    "name": "commerce_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesPurchase amount
agent_idYesAgent making the purchase
currencyNoCurrency codeusd
delegation_idYesCommerce delegation ID
merchant_nameYesMerchant to purchase from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. Addedv2.8.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the tool performs no local pipeline work and returns a deprecation notice rather than a preflight result, which prevents an agent from misreading a successful call as a passing preflight.

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?

Three short sentences, front-loaded with the bracketed '[moved to gateway in SDK 3.3.0]' marker so the deprecation is the first thing read. No padding; the final sentence carries actionable redirection.

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

Completeness4/5

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

For a no-output-schema deprecation stub, the description covers what the tool now does, what it returns in kind, and what to do instead. The only gap is that the gateway endpoint is referenced generically ('the gateway commerce endpoint') rather than by name, leaving the agent to locate it.

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 five parameters (amount, agent_id, delegation_id, merchant_name, currency) are documented in the schema itself. The description adds nothing about parameters, which is defensible for a stub that ignores them, but it also never clarifies that the inputs are inert — so it earns only the baseline 3.

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 states a specific current behavior: the tool no longer runs the 6-gate commerce preflight locally and instead returns a machine-readable deprecation notice pointing to the gateway endpoint. That is far more useful than a tautology, though it describes a stub rather than a capability, so it is clear but not a clean verb+resource action statement.

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?

It explicitly names the two alternatives — compose the pure gate predicates from the SDK, or call the gateway — which tells the agent where to route real work. It stops short of an explicit 'do not call this for actual preflight' prohibition, but the redirect is unambiguous.

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