Skip to main content
Glama

Customs House for Agent Payloads

customs_cross

Cross with a CLEARED filing; issues a signed entry receipt.

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": {
      "filing_id": "<filing_id>",
      "payload": "<payload>"
    },
    "name": "customs_cross"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
filing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It hints at a side effect ('issues a signed entry receipt') but says nothing about idempotency, whether a crossing can be repeated, what permissions are needed, or what happens if the filing is not cleared—critical for a 2-required-parameter mutation.

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 compact clauses, front-loaded with the precondition and ending on the outcome. No filler, though the terseness borders on under-specification rather than efficiency.

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?

For a mutation with no annotations, no output schema, and zero parameter documentation, the description is far too thin. An agent cannot tell what 'payload' should contain or what the returned receipt looks like, so it is not complete enough to call correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only loosely implies filing_id via 'a CLEARED filing'; the required 'payload' parameter is entirely unexplained—its format, content, or role is undocumented anywhere.

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?

States a specific action ('cross') with a resource ('filing') plus a precondition ('CLEARED'), which distinguishes it from siblings like customs_file and customs_status. It stops short of naming those siblings or clarifying what 'cross' produces beyond a receipt.

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 'CLEARED filing' qualifier implies the tool is used after a filing has been approved, which is useful sequencing guidance. However, it never explicitly says when not to use it, nor routes the agent to customs_file/customs_status/customs_verify_receipt as alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources