List every patient-side symptom in the Mediora catalog (fatigue, joint pain, headache, etc.). Returns slug + short name. Use mediora__explain_symptom for the full triage-oriented explainer including the lab work-up a clinician would order.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language code. Defaults to 'en'. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description discloses that it returns a list of all symptoms with slug and short name. No annotations are provided, so description carries the burden—it does well but could mention if the list is exhaustive or any default ordering.
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?
Two sentences: first sentence states purpose and example, second sentence directs to sibling tool. No wasted words, front-loaded with key information.
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?
Given the simplicity (one optional parameter, no output schema), the description fully covers what the tool does and what it returns. No gaps.
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 100% for the single lang parameter, with a clear description in the schema. The tool description does not add additional parameter guidance, but the schema already sufficiently documents it. Baseline 3 is appropriate.
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?
Description clearly states it lists all patient-side symptoms with examples (fatigue, joint pain, headache) and specifies the return format (slug + short name). It also explicitly distinguishes itself from the sibling tool mediora__explain_symptom.
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?
Description explicitly states when to use this tool (to list symptoms) and when to use an alternative (mediora__explain_symptom for detailed explainer with lab work-up). No ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: catalog list/explain tools are divided by entity type (condition, marker, panel, symptom), patient data tools separate history, details, and trend analysis, and analyze_lab_pdf/whoami have unique roles. No two tools could reasonably be confused.
The set overwhelmingly follows a verb_noun pattern (list_*, explain_*, get_*, analyze_lab_pdf, lookup_marker, whoami). The only deviation is 'longitudinal_trend', which is a noun phrase rather than an action verb; still clearly readable.
At 14 tools, the set is well-scoped for a domain that spans catalog browsing, patient data retrieval, and lab report analysis. Each tool serves a distinct purpose and none feel redundant.
The lifecycle is complete: authenticate (whoami), ingest a lab PDF (analyze_lab_pdf), retrieve patient history (get_patient_history), drill into details (get_test_details), and analyze longitudinal patterns (longitudinal_trend). The catalog is fully browsable with list_* and explain_* tools, and lookup_marker bridges aliases. No obvious missing operations.
