Skip to main content
Glama

FarmTempo

items_get

Read-onlyIdempotent

표준 품목 하나 — 소스별 식별자·확정 여부·포장 kg 근거(가격 없음)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_id": "<item_id>"
    },
    "name": "items_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the payload's substance — per-source identifiers, confirmation flag, and kg packaging basis — which matters because there is no output schema. It omits error behavior for unknown item_id, keeping it short of a 5.

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?

A single line with no filler, and the key scope note (no price) is placed at the end where it is still visible. However, the telegraphic fragment style drops information an agent needs, so terseness here borders on under-specification rather than disciplined concision.

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 annotations covering the safety profile and no output schema, describing the returned facets is the right move and it is done partially. Still missing is what item_id must be and what happens on a miss, leaving the definition adequate but not fully self-sufficient for a one-param lookup tool.

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 coverage is 0% for the single param, so the description must carry the meaning of item_id, and it does not: it never says whether item_id is the canonical standard-item id or a source-specific identifier, despite mentioning per-source identifiers in the return. That ambiguity is exactly what an agent needs resolved before calling.

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?

"표준 품목 하나" plus a parenthetical enumerating returned facets (per-source identifiers, confirmation status, packaging kg basis) and the negative scope "가격 없음" makes clear this is a single-item detail fetch, not a price tool. The verb is implied rather than stated, but the combination of the singular scope and the item_id requirement disambiguates it from list/price siblings.

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?

The "가격 없음" (no price) note implicitly routes price questions elsewhere, which is a real usage boundary, but no sibling is named and no when-to-use or when-not-to-use condition is spelled out. An agent must infer that pricing questions belong to get_item_price_history or similar.

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