Skip to main content
Glama

Stratalize Intelligence

Get Value Based Care Performance

get_value_based_care_performance
Read-only

Use when benchmarking VBC contract performance, assessing FFS-to-VBC transition readiness, or preparing a population health strategy presentation. Returns MSSP ACO savings rates, BPCI episode costs, and MIPS quality signal medians. Example: MSSP Track 1 ACOs generating median 2.3% savings above benchmark — top quartile at 4.8% — organizations below 1.5% savings face program exit risk. Source: CMS VBC program data 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_value_based_care_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bed_sizeNo
specialtyNo
program_typeNo
current_vbc_revenue_pctNoPercentage of revenue from value-based contracts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), yet the description still adds real value: the data source (CMS VBC program data composite) and the per-call cost of $0.02 USDC, which is material for an agent deciding whether to call. It doesn't say whether results are per-organization or benchmark medians only, nor anything about latency or caching, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the 'Use when' triggers, then the return contents, then a concrete benchmark example, then provenance and price — each sentence does a distinct job. The MSSP percentile narrative is longer than a bare spec but earns its space by teaching interpretation thresholds (below 1.5% savings = exit risk).

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 must explain what comes back, and it names the metric families plus one illustrative value, which is a decent start. However, it doesn't say whether the response is benchmark medians, per-organization rows, or both, nor how the four optional filters narrow the result — gaps an agent would hit on first 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 only 25%, so the description must carry parameter meaning, and it largely doesn't. It never mentions bed_size, specialty, or what population the parameters filter, and only indirectly alludes to program_type via the MSSP/BPCI/MIPS examples; specialty in particular is left with no taxonomy or expected values in either place.

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 uses a specific verb-plus-resource framing: it returns MSSP ACO savings rates, BPCI episode costs, and MIPS quality signal medians, which makes the tool's output domain concrete. It doesn't name a sibling or state what it is not, so an agent can't distinguish it from e.g. get_cms_facility_benchmark or get_cms_star_rating on the definition 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?

Three explicit 'use when' triggers are given: benchmarking VBC contract performance, assessing FFS-to-VBC transition readiness, and preparing a population health strategy presentation. There are no when-not conditions and no named alternatives, so an agent knows when to reach for it but not when to prefer a neighboring CMS benchmark tool.

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