Search healthcare terminology by name or synonym. Returns matching concepts with a configurable limit.
Search concepts/terminology
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": "searchTerminologyConcepts"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| term | No | ||
| limit | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavioral traits. It does not mention whether the operation is read-only, any side effects, rate limits, or maximum results. The description adds minimal behavioral information.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is overly brief at just one sentence. While concise, it fails to include necessary detail, making it under-specified rather than efficiently complete.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no annotations, and incomplete parameter documentation, the description leaves the agent without enough information to correctly invoke the tool. Missing details like search behavior, max limit, and return format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, meaning parameter descriptions are missing from schema. The description does not explain the meaning or constraints of 'term' or 'limit'. For a search tool, this is a critical gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Search concepts/terminology' is vague and does not specify which concepts or terminology system. It fails to distinguish from sibling tool 'searchOpenMRSConcepts' which is more specific. The verb 'Search' is present but the resource is unclear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'searchOpenMRSConcepts'. The description provides no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.