Skip to main content
Glama

Stratalize Intelligence

Get Pharmacy Spend Benchmark

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.6/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 the description's job is limited. It adds real value by disclosing provenance ('Stratalize static model derived from published 340B savings ranges'), which tells the agent the numbers are modeled rather than customer-specific, and it quotes a per-call price ($0.10 USDC). It does not state coverage limits by state or what happens when optional inputs are omitted.

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 use case before the return list, and every element (outputs, worked example, provenance, price) is decision-relevant. The worked example is long but earns its space by showing the comparison shape; the sentence could be tightened slightly without losing content.

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 correctly spends words on the returned metrics and gives a concrete example, so return-value expectations are covered. However, for a five-parameter tool with zero required inputs and no schema documentation, it leaves the input contract underspecified — an agent cannot tell what an empty call returns versus a fully parameterized one.

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% across five parameters, so the description carries the full burden and largely fails. It only implicitly hints at bed_size ('GPO targets by bed size') and enrolled_340b ('340B eligibility'), leaving state, annual_patient_days, and annual_pharmacy_spend entirely unexplained, and it never says how results change or default when those optional parameters are omitted.

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?

States a specific resource (hospital pharmacy spend benchmark) and enumerates the exact outputs: drug cost per adjusted patient day, 340B savings opportunity, specialty drug drivers, and GPO targets. It does not distinguish itself from plausible siblings such as get_gpo_contract_benchmark or get_cms_facility_benchmark, even though it touches GPO targets, so an agent cannot fully rule out overlap from this text alone.

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?

The opening sentence gives clear situational context: benchmarking hospital pharmacy costs or preparing a board presentation on cost reduction. It stops short of naming when-not to use it or which sibling to pick for adjacent questions (GPO contracts, CMS facility comparisons), so the routing decision is only partly supported.

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