Skip to main content
Glama

FarmTempo

usda_movement_summary

Read-onlyIdempotent

선택한 행들의 파운드 합계.

🔴 이 합계는 USDA 가 발표한 수치가 아니라 팜템포가 더한 값이다. 응답의 computed 가 그렇게 밝힌다. 단위는 파운드 그대로 — kg·톤으로 바꾸지 않는다.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
originNo
group_byNo하나: origin, commodity, entry_point, transport_modeorigin
commodityNo
entry_pointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuine behavioral value beyond that: the total is FarmTempo-computed rather than USDA-published, that fact is surfaced in the response's `computed` field, and the unit must stay in pounds with no kg/ton conversion. That provenance caveat is exactly the kind of context an agent would otherwise get wrong.

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?

It is short and front-loaded: the purpose lands in the first line, then the critical provenance warning. The emoji and bold markup are noise but do not bloat the text; every sentence carries information.

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

Completeness3/5

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

There is no output schema, so the description should describe the return shape. It names the `computed` flag but not what else comes back (total field, group breakdown when group_by is set, behavior with limit). Given 7 loose parameters and no output schema, this leaves real gaps.

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?

With 7 parameters at 14% schema description coverage, only group_by carries any documented meaning. The description mentions 'selected rows' but never explains from/to, origin, commodity, entry_point, or limit — the agent must guess how filters narrow the summation.

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 single line '선택한 행들의 파운드 합계' gives a concrete verb (sum) and resource (pounds over selected rows), which distinguishes it from the row-listing sibling usda_movement. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

Usage is only implied: an agent can infer it should call this when it needs an aggregate total instead of raw records, and that '선택한 행들' means the same filters drive the selection. There is no explicit when-to-use, when-not-to-use, or pointer to usda_movement for per-row detail.

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