Skip to main content
Glama

deathcare_projection

Year-by-year expected deaths for a county, 2025-2040, for service-capacity planning. These are projections, not recorded counts, and uncertainty grows the further out the series runs. Measured backtest over a four-year horizon: median absolute error 4.36%, 87% of counties within 10%. PAID (Professional and above).

Tool call template

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

Input Schema

NameRequiredDescriptionDefault
fipsNo
stateNo
countyNo
to_yearNo
from_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does more than most: it discloses that the values are projections rather than observed counts, warns that uncertainty grows over the horizon, and quantifies accuracy with a concrete backtest (median absolute error 4.36%, 87% of counties within 10%). It also states the access tier. Remaining gaps are the response shape and any rate or volume limits, which matter more because no output schema exists.

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?

The description is three sentences, front-loaded with the core definition, followed by the projection caveat and then the accuracy evidence. Almost every sentence adds information. The trailing 'PAID (Professional and above).' is telegraphic but functional.

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?

The description is adequate about what the numbers are and how trustworthy they are, which is the hard part for a projection tool. However, a tool with five undocumented optional parameters, no annotations, and no output schema needs more: how parameters combine, what the response looks like, and what the default geography or date window is when nothing is supplied. The definition covers the concept but not the practicalities of calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all five parameters (fips, state, county, to_year, from_year), so the description must compensate, and it largely does not. It implies that geography is county-level and that years span 2025-2040, but it never explains whether fips, state, and county are alternatives or complements, nor what happens when a caller omits all of them given that zero parameters are required. An agent still has to guess at invocation semantics.

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 states a specific verb-and-resource pair ('year-by-year expected deaths for a county'), fixes the temporal scope (2025-2040), and distinguishes itself from recorded counts by saying 'These are projections, not recorded counts.' The purpose can be understood without opening the schema. It does not name any sibling tool by name, so the differentiation from deathcare_bulk_extract or deathcare_market is left implicit.

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?

The phrase 'for service-capacity planning' gives a use context, and 'PAID (Professional and above)' signals the tier needed to call it. But there is no explicit when-to-use versus when-to-use-alternatives guidance, no when-not-to-use condition, and no statement of prerequisites beyond the pay tier. Usage is implied rather than prescribed.

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