Skip to main content
Glama

recovery.navigation.get_condition

recovery.navigation.get_condition
Read-onlyIdempotent

Return a published condition record by exact slug. The record is educational and is not a patient-specific diagnosis or treatment plan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "recovery.navigation.get_condition"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
dataYes
resultYes
statusYes
urgencyYes
versionYes
warningsYes
confidenceYes
provenanceYes
limitationsYes
scope_matchYes
missing_dataYes
allowed_actionsYes
clinical_decisionYes
safety_gate_statusYes
requires_clinician_reviewYes
autonomous_clearance_issuedYes
autonomous_clinical_clearanceYes
individualized_prescription_issuedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, so the bar is lower. The description adds genuinely new context: the record is educational and explicitly not a patient-specific diagnosis or treatment plan, which materially shapes how an agent should present the result. It does not mention behavior on a missing or unpublished slug, keeping it from a 5.

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 filler, and the operation and lookup key appear first. The disclaimer sentence is short and carries real informational weight.

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?

With a single required parameter, full annotation coverage, and an output schema handling return values, the description covers what an agent needs. The remaining gap is the absence of guidance for slug resolution and not-found behavior, which is minor at this complexity.

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 0%, so the description must compensate; it does so partially by stressing 'exact slug', signaling exact-match rather than substring lookup. It does not describe where slugs come from or the allowed format (the pattern in the schema is undocumented).

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?

States a specific verb ('Return') and resource ('published condition record') plus the lookup key ('exact slug'). The word 'published' and 'exact' implicitly separate it from the sibling search_conditions tool, but the sibling is never named, leaving a small gap in differentiation.

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

Usage Guidelines3/5

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

'By exact slug' implies this is the direct-lookup path when the slug is already known, which is useful context. However, it never explicitly says when to use this versus recovery.navigation.search_conditions, nor what to do when the slug is unknown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources