Medical Calculator MCP Server

by u9401066

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

find_tools_by_params

Enter available patient parameters to discover which clinical scoring tools can be calculated from them.

Instructions

🔍 根據已有參數找工具 (High-Level 反向查找)

「我有這些數值，可以計算什麼？」

Args: params: 參數名稱列表 Examples: ["creatinine", "age", "weight"] ["gcs", "pupil", "motor"] ["bilirubin", "inr", "ascites"]

Returns: 可使用這些參數的工具清單

Example:

find_tools_by_params(["age", "creatinine", "bilirubin"])
# → {"tools": [
#      {"tool_id": "meld_score", "input_params": [...]},
#      {"tool_id": "ckd_epi_2021", "input_params": [...]},
#      ...
#    ]}

💡 適合場景: 已有病患數據，想知道能計算哪些評分

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.2Sep 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format through an example output, which is helpful, but it does not mention any limitations, behavior on empty results, or performance characteristics. For a simple read-only lookup, this is adequate but not exhaustive.

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?

The description is well-structured with sections for Args, Returns, an example, and a usage tip. Though it uses emojis and extra formatting, every part adds value. It is not overly verbose for the amount of information conveyed.

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?

The tool is simple and the description covers the key aspects: purpose, input examples, return structure, and a typical use case. Although it doesn't discuss error cases or alternative tools, for the given complexity it is sufficiently complete for an agent to call it correctly.

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

Parameters4/5

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

The schema has one parameter 'params' with minimal description (0% schema description coverage). The tool description compensates by providing multiple examples of valid values and clarifying it expects a list of parameter names. This gives the agent a clear understanding of what to pass.

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 clearly states the tool's purpose: reverse lookup of tools given parameters. It provides a title and examples that make the function unmistakable. However, it does not explicitly differentiate from siblings like get_related_tools, which might also appear in a related-context search, so it earns a 4 rather than a 5.

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?

The description includes a '適合場景' (suitable scenario) section that tells the agent when to use it: when the user has patient data and wants to know which scores can be calculated. It also provides multiple concrete examples of parameter lists. It does not mention when not to use it or alternatives, but the guidance is clear enough for a lookup tool.

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

Deploy Server