Skip to main content
Glama

find_judgment_tree

Retrieve a step-by-step classification or pathway decision tree by region and procedure, such as orthopedic implant registration, to guide classification and routing decisions.

Instructions

取分类/路径判定树(逐步问答结构)。演示结构,最终以分类目录与界定结论为准。

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

Input Schema

NameRequiredDescriptionDefault
regionNo地区码,默认 CN
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?

With no annotations, the description carries the full behavioral burden. It usefully discloses that the returned structure is a demonstration and is not the final authority, which is real context beyond the schema, but it says nothing about whether the lookup is read-only, what the response contains beyond Q&A nodes, or any failure behavior.

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?

Two short sentences with no waste: the first states the resource and its structure, the second states the authority caveat. Both are front-loaded and every sentence earns its place.

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 simple two-parameter read lookup with no output schema, the description covers what is returned (a step-by-step Q&A tree) and how much to trust it. It is somewhat thin on how to interpret or traverse the tree, which keeps it short of fully complete.

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%: 'region' is documented as a region code defaulting to CN and 'procedure' is illustrated with an example procedure name. The description adds no further meaning to either parameter, so the schema does the heavy lifting and the baseline of 3 applies.

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 names a specific action and resource: '取分类/路径判定树' (retrieve the classification/pathway decision tree) and adds the output form ('逐步问答结构', a step-by-step Q&A structure). It does not distinguish this tool from siblings such as get_region_path or query_standard, so the agent must infer which retrieval path applies.

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 statement of when to choose this tool over alternatives, nor any prerequisite or exclusion. The only guidance offered is the disclaimer that the tree is illustrative and the classification catalog plus definition conclusions are authoritative, which tells the agent how to weigh the output but not when to call the tool.

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