Skip to main content
Glama

Stratalize Intelligence

Get Travel Nurse Rate Benchmark

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.6/5.0
Behavior3/5

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

Annotations already establish a safe read-only, open-world call, and the description adds genuinely useful context: the data source (BLS plus a Stratalize SIA-style composite) and the per-call price of $0.02 USDC. It does not disclose coverage limits (which states or specialties exist), freshness of the medians, or error behavior for unknown specialties.

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-loads the when-to-use clause and the return shape before the example, which is efficient. The closing ROI claim about recovering $180K-$240K per 10 FTE travelers is promotional padding that does not help an agent call the tool.

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 usefully characterizes the return values (medians, percentile bands, worked ICU/Illinois example) and the cost. The remaining gap is input-side: no enumeration or format hints for the two required arguments on a 0%-coverage schema.

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 schema documents neither parameter, and the description only implies that specialty and state select the benchmark. It gives no format guidance on state (abbreviation vs. full name) or specialty naming conventions, leaving an agent to guess at values that will fail validation upstream.

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: returns bill-rate medians and bands by specialty and state for travel nurse contracts. It is clearly distinguishable in subject matter from generic siblings like get_vendor_market_rate, though it never names an alternative explicitly.

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 a concrete activation context: 'Use when benchmarking travel nurse contract rates or negotiating with a staffing agency.' It does not state when not to use it or point to the healthcare/vendor sibling tools for adjacent cases.

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