Skip to main content
Glama
mcp-taiwan-legal-db

mcp-taiwan-legal-db

by lawchat-oss

search_interpretations

列舉大法官解釋 / 憲法法庭裁判。支援關鍵字全文搜尋(搜爭點 + 理由書)。

Instructions

列舉大法官解釋 / 憲法法庭裁判。支援關鍵字全文搜尋(搜爭點 + 理由書)。

每筆結果帶 case_id,可直接傳給 get_interpretation()。行政機關的函釋、解釋令不在這裡, 用 search_agency_interpretations。

Args: keyword: 關鍵字(標題/字號/爭點/理由書全文匹配) year: 篩選民國年度(0=不篩選,>0 只回新制憲判字) number_from: 起始號次(含),0=不篩選 number_to: 截止號次(含),0=不篩選 include_old: 包含舊制釋字(year=0 時才生效) include_new: 包含新制憲判字 max_results: 回傳筆數上限(預設 30,上限 200)

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

Input Schema

NameRequiredDescriptionDefault
yearNo
keywordNo
number_toNo
include_newNo
include_oldNo
max_resultsNo
number_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses which fields the keyword matches, that results are capped at 200 with a default of 30, that each row carries a case_id for chaining, and the non-obvious gating rule that include_old only takes effect when year=0. It stops short of stating read-only/safety semantics, sort order, or whether a result set was truncated at max_results.

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?

Front-loaded purpose and exclusion sentence first, then the chaining hint, then a compact Args list. Every line adds meaning; there is no filler or restatement of the tool name.

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?

For a 7-parameter search tool with no annotations and no output schema, the definition is nearly sufficient: it describes matching scope, result identity (case_id), and the result cap. Remaining gaps are minor but real — no indication of ordering, total-match count, or how to page past the 200 cap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: every one of the 7 parameters is explained beyond its name, including sentinel semantics (0 = 不篩選) for year/number_from/number_to, inclusive bounds for the number range, the 預設 30 / 上限 200 constraint on max_results, and the year=0 dependency for include_old. This is information the bare schema cannot supply.

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?

States a specific verb+resource pair (列舉大法官解釋/憲法法庭裁判) and immediately scopes it as keyword full-text search over 爭點 + 理由書. It also names what the tool is NOT (agency 函釋/解釋令) and the sibling that handles those, so an agent can distinguish it from search_agency_interpretations and get_interpretation without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes a whole class of queries away to search_agency_interpretations, and explains the follow-up step (pass the returned case_id to get_interpretation). Both the when-to-use-this and when-to-use-something-else conditions are stated, not implied.

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