Skip to main content
Glama

FarmTempo

usda_catalog

Read-onlyIdempotent

팜템포가 재배포 승인을 받아 보유한 USDA AMS Market News 리포트 3종과, 품목별 수록 구간.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds genuinely useful scope context beyond that: only redistribution-approved USDA AMS Market News data is included, exactly three report types, and coverage is bounded per item. It stops short of describing the response shape or ordering, which matters because there is no output schema.

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?

A single compact clause with no filler or repetition, and the most important qualifier (redistribution approval, three report types) comes first. The trade-off is that the extreme brevity leaves the action unstated, edging into under-specification rather than verbosity.

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?

For a no-parameter, read-only catalog with no output schema, the description should at minimum convey what the returned entries look like and how this index relates to the per-dataset catalogs and data tools beside it. It conveys the content scope well but leaves the return structure and sibling relationship for the agent to guess.

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 there is no parameter meaning for the description to carry. Baseline 4 applies; nothing in the description misleads about inputs.

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 identifies the resource as the three USDA AMS Market News reports held under FarmTempo's redistribution approval, plus per-item coverage windows, which is more specific than a restatement of the name. However, it is a bare noun phrase with no verb (it never says 'list' or 'return'), and it does not distinguish itself from the sibling catalogs usda_movement_catalog and usda_sp_catalog. An agent cannot tell from this text whether usda_catalog is the parent index of those or a parallel listing.

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 at all: nothing states that this should be called first to discover what data is available, nor any exclusion against the sibling catalog and data tools. The only implicit signal is the word 'catalog' in the name. With several similarly named USDA tools present, this omission is consequential.

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