Skip to main content
Glama

Sepsis Hospital Outcomes

sepsis_hospital_outcomes
Read-onlyIdempotent

National U.S. inpatient hospital length of stay and mean cost per stay for sepsis (principal diagnosis), by patient population and year, 2016-2021, from AHRQ HCUP Statistical Brief #306. This is the only public AHRQ cross-year table found that reports a 2021-specific national figure. Separately reports any-listed-diagnosis sepsis stay counts (a broader population than principal diagnosis) for the years AHRQ printed a figure (2016, 2019, 2021).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "period": "y2021",
      "population": "all"
    },
    "name": "sepsis_hospital_outcomes"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoReporting period. "y2021" is the full-year 2021 estimate (with and without a co-occurring COVID-19 diagnosis combined). Defaults to "y2021".
populationNoPatient population. Defaults to "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description nonetheless adds real behavioral context: the source publication, that LOS/cost are principal-diagnosis only, that any-listed counts exist only for the years AHRQ printed (2016, 2019, 2021), and that the 2021 figure was uniquely available here. It omits unit and format detail, but coverage gaps and population scope are disclosed.

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?

Two sentences, front-loaded with the dataset, source, and coverage window before the secondary any-listed-count caveat. Dense but every clause carries information; the provenance claim about the 2021-only figure is arguably promotional but helps the agent trust the source.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must convey the return shape, and it does describe what is reported (length of stay, mean cost per stay, stay counts). However, it never states units (days, dollars), how the any-listed counts are keyed relative to the population parameter, or the response structure, leaving real gaps for a data-retrieval tool.

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 coverage is 100% and both enums carry descriptions with defaults, so the schema does the heavy lifting. The description adds the 2016-2021 span and the population dimension but does not explain the avg_2016_2019 aggregation or the _with_covid/_without_covid splits beyond the schema's note on y2021. Baseline 3 is appropriate.

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 the specific resource: national inpatient length of stay and mean cost per stay for sepsis (principal diagnosis) by population and year, sourced from AHRQ HCUP Statistical Brief #306, plus any-listed-diagnosis stay counts. That is far more specific than the name alone. It does not explicitly differentiate itself from the sibling condition_hospital_costs, which an agent could plausibly confuse it with.

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 the data description: query this for sepsis-specific LOS/cost figures. There is no explicit 'use this when' statement and no mention of the obvious alternative (condition_hospital_costs) or when that sibling would be preferred. The principal-vs-any-listed distinction is useful scoping context but is about data interpretation, not tool selection.

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.