Taiwan Road Safety Data (Unofficial)

get_township_drunk_ranking

查詢某縣市某年各鄉鎮的酒駕事故件數與死傷，回該縣市完整的鄉鎮列表（依死傷、案件、鄉鎮名稱排序）；city 不填為屏東縣；口徑是警政署的肇因研判，不是道安總動員的數字，不可互比或推算占全縣市比例，也沒有跨縣市排名；目前只有 114 年，內建離線資料，不連上游

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": {
      "year": "<year>"
    },
    "name": "get_township_drunk_ranking"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No	縣市名稱，22 縣市之一（寫法可用 list_areas 查），不填為屏東縣
`year`	Yes	民國年，目前只有 114

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so well: it names the underlying source caliber (警政署肇因研判), forbids cross-caliber comparison and proportion extrapolation, states the single available year, and notes the tool uses built-in offline data with no upstream connection. It also describes the return shape and sort order (casualties, case count, township name), which an agent needs to interpret results correctly.

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?

Purpose is front-loaded and every clause carries information, but it is one long semicolon-chained sentence, and the 'currently only 114' fact is repeated from the schema. Dense rather than wasteful overall.

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

Completeness5/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's explanation of what is returned (the full township list for the county, sorted by casualties, cases, then name) is essential and present. Combined with the caliber caveats, default city, and year restriction, an agent has enough to call and interpret the tool correctly.

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 description coverage is 100%, so both parameters are already documented in the schema, including the Pingtung default and the year-114-only constraint. The description largely restates those facts rather than adding new semantics, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource with full scope: drunk-driving accident counts and casualties per township for one county and one year, returning the complete township list. It also rules out scope confusion by stating there is no cross-county ranking, so an agent can tell it apart from county-level or ranking-style siblings.

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 gives concrete usage context: city defaults to Pingtung when omitted, only year 114 exists, and the data caliber cannot be compared with 道安總動員 figures or used to derive county-wide proportions. It also points to list_areas for resolving city spellings. What is missing is an explicit 'use X instead when you want county-level or cross-county figures' routing statement.

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

All Taiwan Road Safety Data (Unofficial) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?