Agent Field Kit

get_order

Read-onlyIdempotent

Check an Agent Field Kit order by its Stripe checkout session_id (from create_checkout). Before payment: paid:false with pay_url. After payment: paid:true, a receipt and signed download links (valid 72h, 5 downloads per file). Read-only; never charges.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_order"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, yet the description still adds real behavioral content: the pre-payment return shape (paid:false plus pay_url) and the post-payment return shape (paid:true, receipt, signed links valid 72h, 5 downloads per file). The closing 'Read-only; never charges' reinforces rather than contradicts the annotations.

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

Conciseness5/5

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

Three short clauses, front-loaded with purpose and key source, then the two outcome states. Every phrase carries information — parameters, workflow origin, return contract, and download limits — with no filler.

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

Completeness5/5

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

No output schema exists, but the description effectively documents the return contract for both states, including the 72h link validity and 5-download cap. Combined with one well-explained required parameter and full annotation coverage, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter and schema description coverage is 0%, so the description must carry the meaning — and it does by stating the value comes from Stripe's checkout session (specifically create_checkout). It doesn't restate the cs_live_/cs_test_ pattern the schema already enforces, which is fine, but it could have noted that test-mode IDs return test-mode orders.

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

Purpose5/5

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

States a specific verb ('Check') and resource ('an Agent Field Kit order') together with the exact lookup key (Stripe checkout session_id). It also names the sibling that produces that key ('from create_checkout'), so the agent can place this tool in a workflow without opening any schema.

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 description implies the correct sequence: obtain session_id from create_checkout first, then call this tool, and it explains what result means before vs after payment. It stops short of explicit exclusion language (e.g. 'do not use for refunds or for product lookups — see get_product'), so a 4 rather than a 5.

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

All Agent Field Kit 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?