Skip to main content
Glama

get_billing_coding_risk

Read-only

Use when assessing coding compliance risk before an OIG audit, preparing for a RAC review, or building a revenue integrity program. Returns E/M distribution benchmarks, upcoding risk signals, OIG audit priority themes, and RAC watchlist. Example: Cardiology practice E/M mix at 67% level 4/5 visits vs 48% national benchmark — flagged HIGH upcoding risk — OIG cardiology audit focus active in 2024-2025 cycle. Source: CMS and OIG compliance 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_billing_coding_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
specialtyNo
annual_claim_volumeNo
level_4_5_percentageNoPercentage of E/M claims at level 4 or 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (CMS and OIG compliance composite) and a per-call cost of $0.02 USDC, which an agent needs to reason about invocation. It omits return format and latency, keeping it just short of 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.

Conciseness4/5

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

The definition is front-loaded with the primary 'use when' clause and follows with outputs, an illustrative example, source, and price. The example earns its length by concretizing the output and risk flagging, though it adds bulk that could be trimmed for a schema-driven tool.

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 three-parameter, output-schema-less benchmark tool, the description covers purpose, triggers, output contents, data provenance, and cost—substantially more than annotations alone provide. The main incompleteness is silent treatment of the annual_claim_volume parameter, but overall an agent has enough to invoke it sensibly.

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 33% and the description never explains the parameters directly. The worked example implicitly maps 'Cardiology' to specialty and '67%' to level_4_5_percentage, offering marginal aid, but annual_claim_volume is entirely undocumented in both schema and prose, leaving real ambiguity for a low-coverage tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific assessment objective (coding compliance risk) and enumerates concrete outputs: E/M distribution benchmarks, upcoding risk signals, OIG audit priority themes, and RAC watchlist. An agent can immediately tell this is a billing/coding compliance benchmark tool, distinct from the climate, litigation, and vendor risk siblings.

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?

Explicit 'use when' triggers are given: pre-OIG-audit assessment, RAC review preparation, and revenue integrity program building. There are no when-not conditions or named alternative tools, but the sibling set covers different risk domains, so the absence of routing guidance is a minor gap rather than a real ambiguity.

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