Skip to main content
Glama

get_gpo_contract_benchmark

Read-only

Use when benchmarking GPO contract performance or building a supply chain cost reduction case for a hospital board. Returns typical GPO savings percentage, leakage rate, and top savings categories. Example: Acute care GPO median savings 18% vs non-contract pricing — leakage rate 22% means 1-in-5 purchases bypass contract — leakage above 30% triggers mandatory compliance programs at most health systems. Source: HFMA and CMS composite. $0.02 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_gpo_contract_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

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 cover read-only/non-destructive/open-world, and the description adds traits the schema cannot: the data provenance ('HFMA and CMS composite') and a per-call cost of $0.02 USDC, which matters for an agent deciding whether to spend a call. It also interprets a returned field (leakage >30% triggers compliance programs), adding meaning beyond raw output. Nothing contradicts the annotations.

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-loads the trigger condition and the return payload, then supports them with a concrete illustrative example, provenance, and price. Dense but every clause carries information; the example sentence is long but earns its place by teaching interpretation of the leakage metric.

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?

For a one-optional-param, read-only, no-output-schema tool, the description supplies what an agent needs: trigger scenarios, the shape of the returned metrics, how to read them, provenance, and cost. The only real gap is the undocumented 'category' parameter domain.

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 0% for the single optional 'category' parameter, so the description carries the burden. It never documents the parameter by name or its accepted values, but the worked example ('Acute care GPO median savings 18%') implies the category dimension and gives one plausible value. Partial compensation, not full.

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?

Description pairs a specific verb ('benchmarking') with a specific resource ('GPO contract performance') and explicitly enumerates the returned metrics: savings percentage, leakage rate, and top savings categories. It is clear what the tool does, though it never names the nearest siblings (e.g. get_healthcare_vendor_gpo_diligence, get_hospital_supply_chain_benchmark), so differentiation is left to the caller.

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 two concrete triggering scenarios — benchmarking GPO contract performance and building a cost-reduction case for a hospital board — which is stronger than generic 'use for analysis' phrasing. It stops short of stating when NOT to use it or which adjacent benchmark tool to pick instead.

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