Skip to main content
Glama

FarmTempo

tempo_reference_items

Read-onlyIdempotent

템포 기준 시세가 있는 품목 목록 (aT 도매 정산가 26품목)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety and side-effect profile is fully covered by structured data and the description correctly does not restate it. What the description adds beyond annotations is the bounded size of the result set ('26 items') and the provenance of the prices (aT 도매 정산가), which tells the agent this is a small, fixed, offline catalog rather than a paginated external feed. It does not say whether the list is static or refreshed, nor what an item entry looks like.

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 short sentence with the scope constraint front-loaded and no filler; every element (list, Tempo reference prices, 26 items, aT wholesale settlement price) carries information. The parenthetical is slightly cryptic as to whether 26 is a hard cap or a current count, but that is a minor structural imprecision rather than wasted text.

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 zero-parameter list tool with no output schema, the description covers what the tool is and how large the result is, which is most of what an agent needs. However, it never indicates what identifies each returned item (code, name, unit, grade), which matters because the natural next step is passing one of those identifiers to tempo_reference_price. With no output schema to fall back on, that gap is left entirely to runtime discovery.

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 nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical does usefully characterize the source domain of the fixed set, but no parameter-level meaning is required or missing.

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?

Names a specific resource (품목 목록, list of items) with an explicit scope qualifier: only items that have Tempo reference prices, i.e. the 26 aT wholesale settlement-price items. That scope qualifier is what separates it from tempo_reference_price, which presumably returns a price for a single item, so an agent can tell the two apart without opening a schema. It falls short of 5 only because the sentence is terse and never states the verb explicitly ('returns/lists').

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 or when-not-to-use guidance and no named alternative, even though the sibling set contains several plausible distractors (tempo_reference_price, items_list, items_get, get_wholesale_prices). The agent must infer that this is the catalog/discovery step before querying a specific item's reference price. The implied usage is recoverable from the name-plus-scope, but nothing is stated.

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