Skip to main content
Glama

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine non-annotation context: the data source (CMS VBC program data composite) and a per-call price of $0.02 USDC, both useful for an agent deciding whether to call. It says nothing about freshness, coverage years, or what happens when filters return no cohort.

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?

Well front-loaded: the use-cases sentence comes first, then what is returned, then a worked example, then source and cost. Every sentence carries information, though the numeric example (2.3% median, 4.8% top quartile, 1.5% exit risk) is longer than needed to convey the output shape.

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?

There is no output schema, so the description must carry return-value meaning—and it partly does by naming the three metric families and illustrating a quantile distribution. However, it never explains how the four optional inputs filter or segment the results, nor whether omitting them returns all programs, which matters for correct invocation.

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 only 25%—just current_vbc_revenue_pct is documented—and the description adds nothing about how bed_size, specialty, or program_type shape the returned benchmarks. The enum values for program_type happen to mirror the metrics mentioned (MSSP, BPCI, MIPS), which supplies a little implicit mapping, but it is not stated as parameter guidance. Given four optional filters with low coverage, this is a real gap.

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 domain and deliverables: benchmarking VBC contract performance, returning MSSP ACO savings rates, BPCI episode costs, and MIPS quality medians. An agent can distinguish it from generic facility-benchmark siblings like get_cms_facility_benchmark because it is explicitly framed around value-based-care program metrics. It stops short of naming an alternative it supersedes, so a 4 rather than 5.

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 concrete when-to-use triggers are given: benchmarking VBC contract performance, assessing FFS-to-VBC transition readiness, and preparing a population health strategy presentation. That is clear positive guidance with no exclusions or named alternatives, which is the 4 level.

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