Skip to main content
Glama

FarmTempo

market_ticker

Read-onlyIdempotent

[B2AI] 시세 티커 — 품목·가격(원/kg)·전일 대비 %.

⛔ 표시 시각과 기준일을 반드시 함께 준다. 어제 값을 실시간처럼 보이게 하지 않는다. 박거래 품목(거래 50건·1,000kg 미만)은 등락률이 노이즈라 제외한다 — 제외 수는 응답에 명시.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety is covered. The description adds genuine behavior beyond that: thin-trade items (under 50 trades or 1,000 kg) are silently dropped because their change rates are noise, and the response reports how many were excluded — an unusual and useful disclosure about filtering and result completeness.

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?

Three short, front-loaded lines: what it returns first, the presentation constraint second, the filtering rule third. No filler, and the warning marker makes the hard constraint scannable. Only the emoji/symbol formatting adds slight noise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the return-shape burden and does so reasonably: fields returned, the thin-trade exclusion rule, and the reporting of excluded counts. What is missing is the ordering/default-count behavior implied by `limit` and any note on data freshness or source, which leaves a small gap for a snapshot 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?

The single parameter is `limit`, and schema description coverage is 0% — only a default of 12 and a max of 40 are conveyed structurally. The description never mentions `limit` at all, so it fails to compensate for the coverage gap by explaining what is being limited (items returned? ticker rows?) or how ordering interacts with the cap.

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 states a concrete resource and its payload: a market price ticker returning item, price in KRW/kg, and day-over-day percent change. That is specific enough for an agent to know what comes back, but it never distinguishes itself from price-oriented siblings like get_item_price_history, get_wholesale_prices, or check_deal_price, so the agent must guess which price view this is.

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 implied rather than stated — a 'ticker' suggests a current snapshot, and the warning about always showing display time and reference date plus the thin-trade exclusion hints at appropriate presentation contexts. However, there is no explicit when-to-use or when-not-to-use versus the many sibling price tools, so routing remains inferential.

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