Skip to main content
Glama

get_staffing_agency_markup_analysis

Read-only

Use when evaluating staffing agency pricing or negotiating a travel nurse or locum contract. Returns median markup percentage with low/high band by agency and specialty type. Example: AMN Healthcare median markup 40%, Cross Country 37%, Aya 38% — ICU and OR specialties carry 5-8% premium — agencies billing above 45% markup are 12-18% above market. Source: Stratalize SIA 2024-style composite. $0.50 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_staffing_agency_markup_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
specialtyNo
agency_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the safety profile is covered. The description adds genuinely non-schema information: per-call cost ($0.50 USDC) and data provenance (Stratalize SIA 2024-style composite), plus indicative return values. It does not say whether omitting both parameters returns the full agency table or errors, which matters for a read with zero required params.

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?

Four compact sentences, front-loaded with the trigger and the return shape before the example and the cost. The example figures are illustrative and earn their place by preempting the most common question (what will the numbers look like), though the sentence is dense.

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?

There is no output schema, so the description rightly explains the return shape (median plus low/high band, segmented by agency and specialty) and the pricing model. Only the optional-parameter behavior and data freshness are left unstated for a two-param read-only tool.

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 must carry parameter meaning, and it only partially does. 'By agency and specialty type' implies what agency_name and specialty filter, but it never states accepted specialty values, matching behavior, or defaults when a parameter 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 names a specific resource and return value: median markup percentage with a low/high band, broken out by agency and specialty type. The worked examples (AMN 40%, Cross Country 37%, Aya 38%) make the output concrete enough that an agent can distinguish this from generic benchmark siblings.

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 opens with an explicit trigger: 'Use when evaluating staffing agency pricing or negotiating a travel nurse or locum contract.' That is clear context for invocation, but no exclusions or alternative tools are named for adjacent questions such as bill-rate benchmarking or overall labor cost comparison.

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