Skip to main content
Glama

FarmTempo

items_resolve

Read-onlyIdempotent

자유 텍스트(한/영/일/중 표준명·별칭·소스 원문명) → 표준 품목. 부분 일치 안 함 · 두 축 표기와 근거 포함 · 로트 연결 없음

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": {
      "q": "<q>"
    },
    "name": "items_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description's job is to add what they cannot. It does: exact-match semantics (no partial matching), that results carry two-axis notation plus supporting rationale, and that no lot linkage is returned. These are meaningful operational traits beyond the annotation set; only the exact response shape remains unspecified.

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

Conciseness5/5

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

A single front-loaded line with the input→output mapping first and three separator-delimited constraints after it. Every clause adds distinct information and no words are wasted.

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 two-parameter, no-output-schema read tool the core is covered, but two gaps remain: the locale parameter is completely unaddressed, and phrases like "두 축 표기와 근거" (two-axis notation and rationale) are too compressed for an agent to predict the return payload without an output schema.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. It does clarify what q accepts (multilingual standard names, aliases, source original names), which is real added meaning, but the locale parameter is never mentioned and no format constraints beyond maxLength are given.

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 transformation: free text in Korean/English/Japanese/Chinese (standard names, aliases, source original names) mapped to a standard item. The arrow notation makes the input→output relation unambiguous, so an agent can distinguish it from items_get/items_list. It does not, however, explicitly contrast itself with any named sibling.

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?

"부분 일치 안 함" (no partial matching) is a useful negative constraint that tells the agent not to rely on this for fuzzy lookup, and "로트 연결 없음" signals lots_reconcile is a separate step. But there is no explicit statement of when to prefer this over items_get, items_list, or market search tools, so the usage decision is left to inference.

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