Skip to main content
Glama

FarmTempo

region_list

Read-onlyIdempotent

권역별 상태 + 밀도 지표. 실제 카운트만 — 0인 권역도 0으로 표시한다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive, and they also declare openWorldHint=false. The description adds one genuinely useful behavioral fact beyond them: zero-count regions are still emitted rather than omitted, so the agent knows the output is unfiltered and complete. It stops there and says nothing about ordering, aggregation unit, or how density is computed.

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?

The description consists of two short Korean sentences. The first gives the subject matter and the second gives the non-obvious inclusion rule, which is the right thing to put first after the topic. There is no filler, although the first sentence is terse enough that it borders on cryptic.

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?

There is no output schema, so the description carries the burden of explaining what comes back. It hints at 'status' and 'density metrics' without defining either field or the region identifier. For a zero-parameter read tool, that leaves a real gap for an agent that must interpret the response.

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. There are no arguments whose meaning the description could clarify or obscure.

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 names a resource ('권역별' / by-region) and what it returns ('상태 + 밀도 지표', status plus density metrics), so the general shape is clear. But it never says what is being counted or which domain the regions belong to, and it makes no attempt to distinguish itself from siblings such as get_auction_markets or market_ticker.

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 no when-to-use guidance, no statement of prerequisites, and no named alternative for the cases this tool does not cover. The agent must infer the use case from the title-less name alone.

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