Skip to main content
Glama

FarmTempo

get_auction_markets

Read-onlyIdempotent

경락 조회에 사용할 수 있는 전국 공영도매시장 코드(예: 110001=서울가락)와 한글명 목록. /api/auction/price 의 market 파라미터에 코드·한글명 모두 사용 가능.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: it is a static reference list, and both the code and the Korean name are accepted downstream. It does not mention list size or ordering, but the output schema covers return structure.

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?

Two short sentences with zero filler: the first identifies the resource, the second tells the agent how to use the result. The essential information is front-loaded.

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 zero parameters and an output schema, the description needs only to explain what the list is and how to apply it, which it does. Minor omissions such as whether the list is exhaustive or how large it is are low-risk for a static lookup tool.

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 zero parameters, so the baseline is 4 and there is nothing to clarify. The description does add meaning for the downstream market parameter by stating that either the numeric code or the Korean name is valid.

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 specific resource (전국 공영도매시장 codes and Korean names) and gives a concrete example value (110001=서울가락), so an agent knows exactly what the tool returns. It does not explicitly name a sibling tool, but it points at the /api/auction/price market parameter, which effectively ties it to the price-lookup path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the intended use (경락 조회) and where the results go (the market parameter of /api/auction/price), which is clear context for calling it before a price query. There are no explicit exclusions or negative guidance, but for a zero-parameter reference list there is little else to exclude.

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