Skip to main content
Glama

get_pharmacy_spend_benchmark

Read-only

Use when benchmarking hospital pharmacy costs or building a pharmacy cost reduction strategy for a board presentation. Returns drug cost per adjusted patient day, 340B savings opportunity from published savings ranges, specialty drug drivers, and GPO targets by bed size. Example: 250-bed community hospital — drug cost $287/adjusted patient day vs $241 peer median — 340B eligibility could recover $1.8M annually — specialty drugs driving 61% of cost variance. Source: Stratalize static model derived from published 340B savings ranges. $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
stateNo
bed_sizeNo
enrolled_340bNo
annual_patient_daysNo
annual_pharmacy_spendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: the asset is a 'Stratalize static model derived from published 340B savings ranges' (i.e., not live data) and each call costs '$0.10 USDC per call,' which affects invocation decisions.

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 when-to-use condition is front-loaded, followed by the return payload, a concrete example, provenance, and price — a logical order with little waste. The example sentence is long but earns its place by making the output shape concrete.

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 usefully enumerates what comes back and gives a sample result, which compensates for the missing schema. However, for a five-parameter tool with zero schema documentation and no required fields, the description leaves the agent guessing about parameter behavior and about what happens when called with no arguments.

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?

All five parameters (state, bed_size, enrolled_340b, annual_patient_days, annual_pharmacy_spend) have 0% schema description coverage, so the description carries the full burden and largely fails it. The worked example hints that bed count and 340B eligibility drive the output, but units, defaults, and the fact that all parameters are optional with no required inputs are never explained.

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?

The description uses a specific verb+resource ('benchmarking hospital pharmacy costs') and enumerates the exact returns: drug cost per adjusted patient day, 340B savings opportunity, specialty drug drivers, and GPO targets by bed size. That is clearly distinct from sibling benchmarks such as get_gpo_contract_benchmark or get_cms_facility_benchmark.

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?

It states the trigger conditions explicitly: 'Use when benchmarking hospital pharmacy costs or building a pharmacy cost reduction strategy for a board presentation.' There are no exclusions or named alternatives telling the agent when NOT to use it, so it stops short of a 5.

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