Skip to main content
Glama

FarmTempo

items_list

Read-onlyIdempotent

표준 품목 목록 — 소스별 매핑 신뢰도 요약(가격 없음)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description needn't re-establish that. It does add genuine behavioral context by stating the result is a summary of mapping confidence by source and that prices are excluded. It stops short of describing ordering, shape, or what 'mapping confidence' means numerically.

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 line with the resource front-loaded and the two scoping facts (mapping confidence, no prices) appended. Nothing is wasted, though the dash-clause format means the exclusions arrive after the resource rather than leading.

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 zero parameters, rich annotations, and no output schema, the description carries the burden of explaining the return payload — and '매핑 신뢰도 요약' is left undefined (scale? per source count? shape?). It is adequate to select the tool but thin on what an agent will actually receive.

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 no parameters and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 description names a concrete resource (표준 품목 목록, the standard item list) and scopes its payload as a per-source mapping-confidence summary, then explicitly rules out prices. That negative scoping separates it from the price-oriented siblings without naming any of them, so an agent can tell what it returns. It falls short of a 5 only because it is a bare noun phrase with no verb and no named sibling to contrast against.

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: the '(가격 없음)' note steers price lookups away, and '표준 품목' vs 'market_list_items' suggests a canonical-catalog use case. There is no explicit statement of when to call this instead of items_get, items_resolve, or market_list_items, and no prerequisites or exclusions.

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