Skip to main content
Glama

FarmTempo

usda_movement

Read-onlyIdempotent

보고된 대로의 반입 행. 값은 변형하지 않으며, 행마다 리포트 번호와 리포트 날짜가 붙는다.

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": "usda_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
offsetNo
originNo원산 — 국가(수입) 또는 미국 주
commodityNo
entry_pointNo입항지·통과지 원문

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds meaningful behavior: values are never transformed, and each row carries a report number and report date, which tells the agent to expect report-level provenance fields in the output. It does not discuss ordering, pagination behavior beyond the schema defaults, or what happens with empty filters.

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 short sentences with no filler, and the most useful constraint (values are not transformed) is stated up front. The brevity is appropriate, though the opening fragment is terse enough to be ambiguous about what the tool actually returns.

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 seven-parameter filtering tool with no output schema and low schema coverage, the description is too thin. It explains the pass-through nature of the data but says nothing about the filters, result ordering, pagination, or how an empty filter set behaves — details the agent must have to call it 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 only 29% — origin and entry_point are the only documented properties, and the description adds no meaning for from, to, limit, offset, or commodity. With five of seven parameters undocumented in both places, the description fails to compensate for the coverage gap, leaving date-range semantics and commodity matching behavior undefined.

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

Purpose3/5

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

It states the resource (반입/arrival movement rows) and a key property (values are reported as-is), but it is a noun fragment with no verb and it never distinguishes itself from the closely named siblings usda_movement_catalog and usda_movement_summary. An agent can guess this returns raw movement rows, but cannot confirm the distinction from the description alone.

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 explicit when-to-use guidance and no mention of alternatives. The phrase '보고된 대로의' (as reported) hints at raw-row use versus an aggregate, but the agent is left to infer that usda_movement_summary should be used for aggregates.

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