Skip to main content
Glama

get_condition_outcomes

Read-onlyIdempotent

External-review outcomes for a medical condition: how often insurance denials involving this condition were overturned, plus the most-fought treatments for it.

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

Input Schema

NameRequiredDescriptionDefault
slugYesCondition slug, e.g. 'obesity', 'autism', 'hepatitis-c'

Output Schema

NameRequiredDescriptionDefault
pageNoExisting free information page when a matching record is available.
_noteYes
errorNoLookup error text when _coverage.status is not_found or unsupported.
sourceNo
_coverageYes
conditionNo
decisionsNo
overturnedNo
overturn_rate_pctNo
most_fought_treatmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "_coverage": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "applicability": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "jurisdiction": {
      +              "type": "string"
      +            },
      +            "personal_deadline_calculated": {
      +              "const": false,
      +              "type": "boolean"
      +            },
      +            "scope": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "jurisdiction",
      +            "scope",
      +            "personal_deadline_calculated"
      +          ],
      +          "type": "object"
      +        },
      +        "content_reviewed_at": {
      +          "anyOf": [
      +            {
      +              "format": "date",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "YYYY-MM-DD only when this specific content has an existing review date; null means no response-wide review date is asserted."
      +        },
      +        "continuation": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "label": {
      +              "type": "string"
      +            },
      +            "url": {
      +              "$ref": "#/properties/_coverage/properties/sources/items/properties/url"
      +            }
      +          },
      +          "required": [
      +            "label",
      +            "url"
      +          ],
      +          "type": "object"
      +        },
      +        "limitations": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "schema_version": {
      +          "const": "1.0",
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "label": {
      +                "type": "string"
      +              },
      +              "role": {
      +                "enum": [
      +                  "primary_source",
      +                  "publisher_data",
      +                  "curated_guidance",
      +                  "methodology"
      +                ],
      +                "type": "string"
      +              },
      +              "url": {
      +                "format": "uri",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "label",
      +              "url",
      +              "role"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "status": {
      +          "enum": [
      +            "ok",
      +            "no_matches",
      +            "not_found",
      +            "needs_context",
      +            "unsupported"
      +          ],
      +          "type": "string"
      +        },
      +        "summary": {
      +          "type": "string"
      +        },
      +        "tool": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "schema_version",
      +        "tool",
      +        "content_reviewed_at",
      +        "status",
      +        "summary",
      +        "applicability",
      +        "sources",
      +        "continuation",
      +        "limitations"
      +      ],
      +      "type": "object"
      +    },
      +    "_note": {
      +      "type": "string"
      +    },
      +    "condition": {
      +      "type": "string"
      +    },
      +    "decisions": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "error": {
      +      "description": "Lookup error text when _coverage.status is not_found or unsupported.",
      +      "type": "string"
      +    },
      +    "most_fought_treatments": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "overturned": {
      +            "$ref": "#/properties/decisions"
      +          },
      +          "total": {
      +            "$ref": "#/properties/decisions"
      +          }
      +        },
      +        "required": [
      +          "total",
      +          "overturned"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "overturn_rate_pct": {
      +      "anyOf": [
      +        {
      +          "maximum": 100,
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "overturned": {
      +      "$ref": "#/properties/decisions"
      +    },
      +    "page": {
      +      "$ref": "#/properties/_coverage/properties/sources/items/properties/url",
      +      "description": "Existing free information page when a matching record is available."
      +    },
      +    "source": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "name": {
      +          "type": "string"
      +        },
      +        "records": {
      +          "$ref": "#/properties/decisions"
      +        },
      +        "url": {
      +          "$ref": "#/properties/_coverage/properties/sources/items/properties/url"
      +        },
      +        "yearsCovered": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "url",
      +        "records",
      +        "yearsCovered"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "_note",
      +    "_coverage"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's added value is telling the agent the response is aggregate statistical content (overturn frequency, most-fought treatments) rather than raw cases, which is useful framing. It says nothing about result shape, sample size, or coverage limits, so credit is moderate.

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?

A single well-formed sentence that front-loads what the tool returns and wastes no words. Nothing is duplicated or padded.

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?

An output schema exists, so return values need not be explained, and the single parameter is fully documented in the schema. The only meaningful gap is sibling disambiguation against the closely named get_treatment_outcomes and search_outcomes.

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?

With one parameter at 100% schema description coverage (including example slugs like 'obesity', 'autism', 'hepatitis-c'), the schema already carries parameter meaning. The description only implies the slug identifies the condition, adding no format or lookup-failure guidance beyond the schema.

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 resource (external-review outcomes for a medical condition) and enumerates its contents: denial overturn rates plus most-fought treatments. It is clearly a read/aggregate lookup. It stops short of distinguishing itself from siblings like get_treatment_outcomes, whose name suggests overlapping subject matter.

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?

Usage is implied by 'for a medical condition' — you call it when you need outcome statistics for a condition. There is no explicit when-to-use versus when-to-use-something-else guidance, and no help choosing between this tool and get_treatment_outcomes or search_outcomes.

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