Skip to main content
Glama

get_ehr_cost_per_bed

Read-only

Use when benchmarking EHR maintenance costs before a contract renewal or evaluating health IT budget efficiency. Returns benchmark cost per licensed bed with optional gap analysis when actual cost and bed count are provided. Example: Epic maintenance median $4,500/bed — 300-bed hospital at $6,200/bed is 38% above market — renegotiation trigger especially strong at 5+ year renewal cycles. Source: KLAS 2024, Kaufman Hall EHR TCO composite. $0.02 USDC per call.

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": {
      "vendor_name": "<vendor_name>"
    },
    "name": "get_ehr_cost_per_bed"
  }
}

Input Schema

NameRequiredDescriptionDefault
bed_countNo
annual_costNo
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context: the data sources (KLAS 2024, Kaufman Hall TCO composite) and a per-call price of $0.02 USDC, which an agent needs for cost-aware routing. It does not describe pagination or freshness/refresh cadence beyond the source year.

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?

Front-loaded with the trigger condition, then the return, then a concrete worked example, then provenance and price. The example and pricing sentence are long but each carries actionable information; nothing is pure filler.

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 no output schema, the description still conveys the shape of the result (cost per bed plus a percentage gap versus market when inputs are supplied) and the data provenance. A 3-parameter read-only tool is adequately covered, though vendor_name's expected format is left unspecified.

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

Parameters4/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, and it largely does: it explains that gap analysis requires both actual annual cost and bed count, mapping those to two of the three parameters, and vendor_name is implicitly required by the benchmark framing. It could be sharper about whether vendor_name must match a known vendor list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns benchmark EHR maintenance cost per licensed bed, with optional gap analysis. This is clearly distinguishable from the sibling benchmarks (construction, shipping, audit fees, etc.), which cover different cost domains.

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

Usage Guidelines4/5

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

Gives explicit triggers — before a contract renewal or when evaluating health IT budget efficiency — and even a scenario (5+ year renewal cycles) where the signal is strongest. It stops short of naming an alternative tool or stating when not to use it, but the domain is narrow enough that the context is clear.

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