Skip to main content
Glama

FarmTempo

usda_sp_catalog

Read-onlyIdempotent

팜템포가 재배포 승인을 받아 보유한 USDA 산지(shipping point) 리포트와, 품목별 수록 구간.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds genuinely non-structured context — that only reports cleared for redistribution are included — but says nothing about coverage gaps, staleness, or how the per-item ranges are bounded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, which is good. But the phrasing is compressed to the point of ambiguity — the conjunction 'and' leaves unclear whether reports and per-item ranges are one combined listing or two separate concepts, and nothing is front-loaded as an action.

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?

With no parameters, no output schema, and only a read-only annotation set, the description should be the sole source of what a caller receives. It conveys the domain scope but not the shape of the result — whether it returns item identifiers, report names, date boundaries, or all of these.

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

Parameters4/5

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

The tool takes zero parameters, so parameter semantics carry no burden and the baseline of 4 applies. The description correctly implies a no-argument, whole-catalog call rather than a filtered query.

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?

The description names the resource precisely — USDA shipping point reports held under redistribution approval, plus per-item coverage periods — which separates it from the price/series siblings. However it is a bare noun phrase with no verb, so whether the tool lists, searches, or returns the catalog is left implicit.

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 when-to-use guidance and no mention of alternatives such as usda_sp_latest or usda_sp_prices. The agent must infer that this is the index tool consulted before fetching actual report data.

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