Skip to main content
Glama

FarmTempo

tempo_reference_price

Read-onlyIdempotent

플랫폼·AI 에이전트가 거래 가격의 기준으로 쓰는 값. 정의가 고정돼 있고(method_version), 출처·기준일을 함께 준다. 납품가는 운송·포장·등급 차이를 계수로 감안할 것. 결정은 사람.

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": "<item>"
    },
    "name": "tempo_reference_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes품목명 (예: 오이) — /api/v1/reference/items 참고

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that the definition is version-pinned (method_version) and that provenance fields (source, reference date) accompany the value, which is genuine context beyond the annotations. It still says nothing about units, response shape, or behavior for an unknown item.

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?

Four short sentences with no filler, but the opening sentence describes the concept rather than the operation, so the most actionable information (what you get back and the coefficient caveat) is not front-loaded.

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 no output schema, the description must carry the return-value burden, and it only loosely does so: it names source and reference date but not units, currency, or the shape of the payload. For a single-parameter read tool this is adequate but leaves an agent guessing at the output.

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 100% and the single 'item' parameter already carries a description with an example and a pointer to /api/v1/reference/items. The description adds no further meaning about the parameter, so the baseline 3 applies.

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 explains what the returned value represents (a fixed-definition price baseline with provenance) but never states the action plainly: that calling it with an item name returns that item's reference price. It also offers no differentiation from nearby siblings such as check_deal_price, get_wholesale_prices, or tempo_reference_items, leaving the agent to infer the boundary.

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 a caveat about how to treat the result ('납품가는 운송·포장·등급 차이를 계수로 감안할 것') and a decision-authority note ('결정은 사람'), which is useful framing. However, there is no statement of when to call this tool versus the many alternative price tools, and no preconditions 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