Skip to main content
Glama

get_travel_nurse_rate_benchmark

Read-only

Use when benchmarking travel nurse contract rates or negotiating with a staffing agency. Returns bill-rate medians and bands by specialty and state. Example: ICU travel nurse median bill rate $95/hr in Illinois, p75 $108/hr — agencies billing above $115/hr are 21% above market — renegotiation typically recovers $180K-$240K annually per 10 FTE travelers. Source: BLS and Stratalize SIA-style composite. $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>",
      "state": "<state>"
    },
    "name": "get_travel_nurse_rate_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
specialtyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds real context beyond that: the data provenance (BLS and Stratalize SIA-style composite) and an explicit per-call price of $0.02 USDC, which matters for an agent deciding whether to call. It still says nothing about latency, data freshness/vintage, or failure modes when a specialty/state pair has no data.

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 a 'Use when' clause, then the return shape, then an illustrative example, source, and price — a sensible order with no filler sentences. The '$180K-$240K annually per 10 FTE travelers' recovery claim is promotional and unverifiable, which slightly weakens an otherwise tight paragraph.

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 must describe returns, and it does reasonably well (medians, bands, p75, a numeric example). However, for a two-parameter tool with zero schema documentation, it should specify accepted specialty and state formats and mention behavior for unknown or unsupported inputs.

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% for both required parameters, so the description carries the burden. It does imply the two breakdown dimensions and the worked example hints at value format ('ICU', 'Illinois'), but it never states whether specialty is free text or a fixed list, nor whether state must be a two-letter code versus a full name — a real risk of malformed calls.

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?

States a specific verb and resource — 'Returns bill-rate medians and bands by specialty and state' — plus an explicit use condition (benchmarking travel nurse contract rates, agency negotiation). The healthcare-staffing domain cleanly separates it from the many financial benchmark siblings such as get_fx_rate_benchmark or get_cap_rate_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?

Gives clear when-to-use guidance with two concrete scenarios (benchmarking contract rates, negotiating with a staffing agency). It does not name a when-not condition or point at any alternative tool, which keeps it below 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