Skip to main content
Glama

Stratalize Intelligence

Get Billing Coding Risk

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 cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely new behavioral context: the output dimensions, the CMS/OIG composite data source, and a per-call cost of $0.02 USDC. It stops short of covering coverage limits, data freshness, or what happens with partial/no inputs.

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?

Front-loaded with the use-when clause, then returns, then a worked example, source, and price — a sensible ordering. The worked example with fabricated benchmark numbers is longer than strictly necessary but earns its place by illustrating the risk-flagging output.

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?

With no output schema, the description does the work of enumerating returned fields and citing the data source, plus discloses pricing. What's missing is invocation guidance for a tool where all three parameters are optional — an agent can't tell whether omitted inputs yield a general benchmark or an error.

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%: only level_4_5_percentage is documented. The description never explains what specialty strings are accepted (no enums) or what annual_claim_volume is used for. The Cardiology example hints at specialty usage but leaves two of three parameters effectively unspecified.

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?

Names a specific domain and a concrete set of outputs: E/M distribution benchmarks, upcoding risk signals, OIG audit priority themes, and a RAC watchlist. The verb-plus-resource is unambiguous and clearly separable from generic siblings like get_climate_risk_benchmark or get_cms_facility_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?

Explicitly states the triggering situations: pre-OIG-audit compliance assessment, RAC review preparation, and revenue integrity program building. It gives clear when-to-use context but names no alternatives or when-not-to-use conditions.

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