Skip to main content
Glama

BRAINIAC Tariffs & Trade Reference

Explain a US customs bond type

trade-tariff_customs-bond-type-explain
Read-onlyIdempotent

Return a short structured explanation of common CBP customs bond forms and activity codes from public CBP bond concepts. Price $0.02 USDC. POST /api/v1/trade-tariff/customs-bond-type-explain. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trade-tariff_customs-bond-type-explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
bondTypeNobondType, string, one of continuous, single_transaction, activity_1, activity_2, activity_3, activity_4. Required.unknown

Output Schema

NameRequiredDescriptionDefault
titleNotitle. String.
sourcesNosources. Array.
summaryNosummary. String.
bondTypeNobondType. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
typicalUsesNotypicalUses. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: the $0.02 USDC price and the fact that an unpaid call returns x402 payment terms without executing. It does not describe output shape, but an output schema exists to cover that.

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 with the core purpose front-loaded, followed by cost and failure mode. The raw endpoint path is the least useful element for an agent but is brief and does not bloat the definition.

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 one-parameter read-only explainer with an output schema, this covers what the agent needs: what it returns, what it costs, and what happens when unpaid. The gap is the absence of guidance on how the enum values map to the explanations returned.

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 coverage is 100% and the single parameter is a fully documented enum, so the schema carries the semantic load. The description adds nothing about what each bondType value means or how 'unknown' behaves, which is a missed opportunity given the tool's explanatory purpose.

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 names a specific verb and resource: returning a structured explanation of common CBP customs bond forms and activity codes. That is clearly distinct from the sibling lookup and validator tools. It stops short of explicitly contrasting itself with any sibling, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when an agent should call this tool versus the sibling tariff lookups, nor any statement about prerequisites such as needing a funded wallet. The only conditional behavior described is the unpaid-call path, which is about payment mechanics rather than tool selection.

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