Skip to main content
Glama

Stratalize Intelligence

Get Physician Group Benchmark

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.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, open-world lookup. The description adds useful behavioral context: the metric is median total compensation, the source is BLS OES 2024, and each call costs $0.02 USDC, though it omits data limitations and missing-value behavior.

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 description is front-loaded with the main use cases and return metric, followed by an example, source, and price. The retention-risk detail in the example is slightly promotional but still compact and relevant.

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 simple two-parameter benchmark tool with no output schema and clear read-only annotations, the description supplies the output metric, source, price, and examples. It is not fully complete because parameter formats and optional-state behavior remain unspecified.

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?

The schema description coverage is 0%, so the description must explain parameter meaning. It mentions specialty and state and gives examples like Illinois cardiologist and interventional cardiology, but it does not define accepted formats, whether state is optional, or what happens when state is omitted.

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 verb and resource: returns median total compensation by specialty and state. It clearly distinguishes this physician-group benchmark from the many other domain-specific benchmark tools.

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?

It gives explicit use cases such as evaluating physician employment agreements, benchmarking recruitment compensation, and preparing compensation reports. It does not state when not to use it or name an alternative, but the usage context is clear.

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