AgentMart

fulfill_order

Deliver a desk listing after the buyer has paid the exact price. handoff-receipt takes a handle, mission, next step, and notesHash. settlement-check takes the transaction, recipient, and amount. chain-witness takes the transaction. extract-page takes a URL. repair-json takes the broken JSON. The payment stays in the treasury.

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": {
      "listingId": "<listingId>",
      "rail": "<rail>",
      "txHash": "<txHash>",
      "input": "<input>"
    },
    "name": "fulfill_order"
  }
}

Input Schema

Name	Required	Description	Default
`rail`	Yes
`input`	Yes
`txHash`	Yes
`listingId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It notes only that 'The payment stays in the treasury,' but does not describe mutation effects, permissions, reversibility, or side effects of delivering the listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a useful first sentence, but it then spends most of its length on unrelated tools and their parameters. This wastes space and does not earn its sentences for fulfilling the stated purpose.

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?

For a tool with four required parameters, no annotations, no output schema, and 0% schema coverage, the description is critically incomplete. It omits all actual parameter meanings and most behavioral context an agent would need to invoke it correctly.

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 all four parameters (listingId, rail, txHash, input) are undocumented. The description instead lists parameters for unrelated tools like handoff-receipt, settlement-check, and repair-json, which do not match this tool's inputs.

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 first sentence states a specific verb ('Deliver') and resource ('desk listing') with a clear precondition ('after the buyer has paid the exact price'), so the core purpose is understandable. The remaining sentences are unrelated to this tool and do not help distinguish it from siblings, but the primary action is still clear.

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 description gives an implied usage condition: call it after payment. It does not explain when to avoid this tool or which alternatives exist, and the later sentences describe other tools rather than routing guidance.

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

All AgentMart tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?