Skip to main content
Glama

get_asc_benchmark

Read-only

Use when benchmarking ASC financial performance, evaluating an ASC acquisition, or preparing an administrator board report. Returns cost per case medians and revenue mix percentages by specialty. Example: Orthopedic ASC cost per case median $4,200 — facilities above $5,100 are in the bottom cost quartile — orthopedic mix at 60% of cases maximizes margin vs ophthalmology-heavy mix. Source: ASCA and CMS 2024 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_asc_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
specialtyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive, open-world read, so the description's added value is data provenance ('ASCA and CMS 2024 composite') and cost ('$0.02 USDC per call'), both of which matter for agent planning and are absent from annotations. It does not discuss rate limits, response size, or what happens with partial inputs, so it stops short of full transparency.

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

Conciseness3/5

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

Usage conditions are correctly front-loaded, and the pricing note earns its place. However, the dense run-on example with three embedded numeric claims mixes illustration with interpretation guidance and makes the middle of the definition hard to parse.

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 usefully declares what comes back (cost per case medians, revenue mix percentages) and cites a source. It still leaves the 'state' parameter unexplained and gives no sense of result granularity or fallback behavior, which is a real gap for a two-parameter lookup tool.

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 0% for both parameters, so the description must carry the burden. It implies the 'specialty' dimension ('by specialty', orthopedic example) but never mentions the 'state' parameter at all and does not say what happens when either optional argument is omitted.

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?

States a specific verb and resource: it returns 'cost per case medians and revenue mix percentages by specialty' for ASC financials. That clearly separates it from generic benchmark siblings, though it never explicitly contrasts itself with the closest alternatives such as get_cms_facility_benchmark or get_hospital_supply_chain_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?

Names three concrete triggering scenarios: benchmarking ASC financial performance, evaluating an ASC acquisition, and preparing an administrator board report. It gives no exclusions or explicit alternative tools, so an agent knows when to use it but not when to prefer a sibling instead.

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