Skip to main content
Glama

get_region_path

Retrieve the regulatory path for a region code, including accepting authority, route explanation, and required materials checklist for an optional procedure.

Instructions

取地区路径:受理机关、路径说明与该程序的必备材料清单。

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": {
      "region": "<region>"
    },
    "name": "get_region_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes地区码,如 CN、CN-JS
procedureNo程序名(可选)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the returned content fields (a genuine addition over structured data), and "取" implies a read-only lookup, but it says nothing about auth requirements, behavior for unknown region codes, or whether results are cached/localized.

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 purpose first and the returned contents after the colon — no filler. It is efficient, though the compact phrasing compresses several distinct ideas into one line at some cost to scannability.

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?

For a two-parameter read tool with no annotations and no output schema, the description does enough to convey what comes back, which is the most important gap it must fill. It remains incomplete on failure modes and on the optional-parameter branch, which is the minimum-viable level rather than a thorough one.

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 100%, so the baseline is 3, and the description adds only a thin semantic layer: it implies that procedure selects which required-materials checklist is returned. It never explains what the response looks like when procedure is omitted, so it does not meaningfully enrich the schema's "程序名(可选)".

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+resource ("取地区路径") and then enumerates the payload: accepting authority, path description, and the procedure's required materials checklist. That is enough for an agent to know what it retrieves, though it never contrasts itself with any sibling tool.

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 only implied — an agent must infer that this is the lookup for region-specific procedural routing and material requirements. There is no explicit when-to-use, no statement about what changes when the optional procedure is omitted, and no named alternative for overlapping lookups such as query_standard.

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