Skip to main content
Glama

suggest_regions

Recommend k regions with clearly contrasting indicator values from supplied data, so you can build a discriminating set for comparison, mapping, or exam questions.

Instructions

지표 값이 서로 뚜렷하게 갈리는 지역 k곳을 추천한다(판별이 잘 되는 조합).

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": {
      "rows": "<rows>",
      "indicators": "<indicators>"
    },
    "name": "suggest_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
rowsYesfind_data 결과의 rows
indicatorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints at a non-trivial selection heuristic (maximally separating indicator values), but says nothing about determinism, tie-breaking, what happens when k exceeds available rows, or required prerequisites such as rows coming from find_data.

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?

A single front-loaded sentence with the selection criterion in parentheses; nothing is wasted. It is arguably too terse for the missing behavioral detail, but the phrasing itself is efficient.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter analytical tool with no annotations, no output schema, and 33% schema coverage, the description omits the required input provenance, the return shape, and edge-case behavior. The single sentence is insufficient for correct invocation.

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 coverage is only 33%, so the description must compensate. It does explain k ('k곳') and ties the tool to indicator values, but the critical rows parameter is explained only by the schema's 'find_data 결과의 rows' note, and indicators' relation to values keys is left implicit.

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 gives a specific verb and resource ('지역 k곳을 추천한다') plus the selection criterion ('지표 값이 서로 뚜렷하게 갈리는', '판별이 잘 되는 조합'). It is clearly distinct from list_regions in intent, though it doesn't name that sibling explicitly.

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?

No when-to-use or when-not-to-use guidance is given, and the obvious alternative (list_regions, which presumably returns regions without discrimination-based selection) is never mentioned. An agent must infer from the name alone whether to call this or list_regions first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.