Skip to main content
Glama

BRAINIAC Freight & Customs

Extract Incoterms obligations

freight-customs_incoterms-obligation-extract

Read a named Incoterms rule and its named place from the request. The obligation text is that named rule. No duty amount is calculated. Price $0.04 USDC. POST /api/v1/freight-customs/incoterms-obligation-extract. Unpaid calls return 402 and do 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": "freight-customs_incoterms-obligation-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo
incotermNo
namedPlaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose several operational traits: fixed price of $0.04 USDC, HTTP POST endpoint, and that unpaid calls return 402 and do not execute. However, it says nothing about what the response contains, whether file/text inputs are parsed, or whether the call is read-only with respect to any stored state.

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?

The description is short, front-loaded with the core behavior, and every sentence carries practical information (input source, exclusion, price, endpoint, payment gate). The sentence 'The obligation text is that named rule' is slightly awkward and could be rephrased, but there is no padding.

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?

With no output schema, the description should explain what an obligation extraction returns, but it only gestures at 'obligation text'. It also leaves the nested file object and the text parameter unexplained, which matters because all four parameters are optional and the agent has no rule for choosing between document input and named-rule input.

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% across four parameters, including a nested file object with mediaType and base64 content, yet the description only explains incoterm and namedPlace. It never clarifies what file or text inputs are for, whether they are alternatives to the named rule, or that all parameters are optional. This does not compensate for the coverage gap.

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 verb and resource: read a named Incoterms rule plus named place and return the obligation text for that rule. It also excludes duty calculation, which separates it from pricing/duty siblings. It stops short of saying explicitly whether the tool looks up a static rule table or interprets an uploaded document.

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 line 'No duty amount is calculated' implies this is not the tool for duty costing, which is a useful exclusion, but no sibling is named and no explicit when-to-use condition is given. An agent must infer that this is the lookup path for Incoterms obligations rather than a validation or calculation step.

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