Skip to main content
Glama

Stratalize Governance

Get Healthcare Vendor Market Rate

get_healthcare_vendor_market_rate
Read-only

Use when benchmarking a healthcare vendor quote or preparing a supply chain contract negotiation. Returns market rates for EHR, staffing, food service, waste management, and med-surg by facility type. Example: Healthcare food service median $18.40/patient day for acute care — facilities above $22/patient day are 20% above market — GPO competitive rebid typically recovers 8-12%. Source: CMS and Stratalize healthcare vendor 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_healthcare_vendor_market_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this as a safe read-only open-world lookup, so the lower bar applies. The description adds genuine context beyond them: named data sources (CMS and Stratalize composite), a per-call price of $0.02 USDC, and a sample return value. It does not cover failure modes, coverage limits, or data freshness.

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?

Usage trigger is front-loaded, followed by what is returned, a worked example, provenance, and price in that order. The example sentence is long and number-dense but every element adds information an agent would otherwise lack.

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 and 0% schema coverage, the description does most of the work and mostly succeeds by describing return content with sample figures. The remaining gap is the category parameter's accepted values and the shape of the response beyond a single benchmark figure.

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 description coverage is 0%, so the description must carry the load. It implicitly maps the category parameter by listing supported categories and makes clear that a vendor name is the subject, but it never states allowed category strings, whether category is optional, or how a vendor name should be formatted. Partial compensation only.

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 and resource ('Returns market rates'), enumerates the covered categories (EHR, staffing, food service, waste management, med-surg), and scopes results by facility type. It does not explicitly distinguish itself from the generic sibling get_vendor_market_rate, leaving that differentiation to the reader.

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?

'Use when benchmarking a healthcare vendor quote or preparing a supply chain contract negotiation' gives two concrete triggering situations. There are no exclusions or named alternatives telling the agent when to pick a sibling tool instead, so it stops short of full routing guidance.

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