Skip to main content
Glama

Stratalize Intelligence

Get Gpo Contract Benchmark

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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description adds value with data provenance ('HFMA and CMS composite') and a per-call price ($0.02 USDC), which is actionable cost information an agent cannot get from structured fields. It does not describe latency, caching, or data vintage, which would have pushed it higher.

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 usage trigger is front-loaded, followed by the return contents, a concrete example, provenance, and price, in a logical order with no filler. The example sentence is dense with numbers but each illustrates a specific returned metric, so it largely earns its space.

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 does the work of describing returns and adds source and cost, which is good. However, the one input parameter is left undefined and there is no note on whether results are static reference benchmarks or refreshed data, leaving a meaningful gap for a paid benchmark call.

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 the single optional 'category' parameter, and the description never explains what it accepts or how it changes results. The worked example ('Acute care GPO median savings 18%') hints that category values may be care settings, but that requires inference rather than being stated. With such low coverage the description should have compensated and does not.

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 names a specific verb+resource combination (benchmarking GPO contract performance) and enumerates the exact metrics returned: typical savings percentage, leakage rate, and top savings categories. It is not tautological, but it never explicitly distinguishes itself from the closely related siblings such as get_healthcare_vendor_gpo_diligence or get_hospital_supply_chain_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 gives an explicit triggering context: 'Use when benchmarking GPO contract performance or building a supply chain cost reduction case for a hospital board.' That is real when-to-use guidance, but there are no when-not conditions and no named alternatives for adjacent questions like vendor-level GPO diligence.

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