Skip to main content
Glama

get_physician_group_benchmark

Read-only

Use when evaluating physician employment agreements, benchmarking compensation for recruitment, or preparing a medical staff compensation report. Returns median total compensation by specialty and state from BLS OES 2024 data. Example: Illinois cardiologist median $461K total compensation — interventional cardiology 34% above general cardiology — organizations below 25th percentile face retention risk in competitive markets. Source: BLS Occupational Employment Statistics. $0.02 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "specialty": "<specialty>"
    },
    "name": "get_physician_group_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
specialtyYes

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 declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds context annotations cannot carry: the data source and vintage (BLS OES 2024) and an explicit per-call price of $0.02 USDC, which matters for cost-aware agents. It does not discuss caching, fallback behavior, or data lag, keeping 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.

Conciseness4/5

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

It is front-loaded with the usage trigger, then the return content, then an illustrative example, source, and price. The Illinois cardiology example is a long single sentence but earns its place by showing output scale and a percentile-based interpretation.

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 and zero parameter documentation, the description must explain the return surface itself. It mentions medians, but the example also implies percentile bands and retention-risk framing without clarifying whether those figures are returned or merely interpretable. Source, cost, and use cases are covered; return-field detail and parameter formats are not.

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 0%, so the description carries the burden, and it only tells us the results are keyed 'by specialty and state' — with no format guidance (two-letter state code vs. full name, exact specialty naming). It never says state is optional or what happens when it is omitted, leaving the required/optional asymmetry visible only in the schema.

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 states a specific resource and measure: 'median total compensation by specialty and state from BLS OES 2024 data.' That scope is unambiguous and clearly separates it from sibling benchmark tools covering commodities, credit spreads, or facility costs.

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 use cases are named (physician employment agreements, recruitment benchmarking, medical staff compensation reports), which gives an agent a clear trigger. It stops short of exclusions or pointing to an alternative tool when the question is not physician-specific, so it falls short of a 5.

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