Skip to main content
Glama

Stratalize Intelligence

Get Staffing Agency Markup Analysis

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

B3.4/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 useful non-schema context: the data source (Stratalize SIA 2024-style composite) and a per-call cost of $0.50 USDC, which matters for an agent deciding whether to invoke. It does not say how the composite is refreshed, how stale the data can be, or how the low/high band is computed.

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 trigger condition is front-loaded, followed by the return shape, a concrete example, provenance, and price. Every element is relevant, though the example sentence is dense and the provenance/price tail could be separated for scannability.

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 usefully characterizes the return values (median plus low/high band by agency and specialty) and supplies realistic magnitude expectations. However, for a two-parameter tool with zero schema coverage, it leaves the agent guessing about optional-parameter semantics and default behavior when filters are omitted, which is a material gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and both parameters (specialty, agency_name) are undocumented in the schema, so the description carries the full burden. It never explains what values to pass, whether omitting them returns all agencies/all specialties, or how partial matches work. The examples ("AMN Healthcare", "ICU", "OR") hint at expected value formats but do not define parameter behavior or defaults.

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?

The description states a specific verb and resource: it returns median markup percentage with a low/high band by agency and specialty type, which is far more concrete than the tool name alone. The domain (travel nurse/locum staffing pricing) makes it distinguishable in practice from generic benchmark siblings, though it never names a sibling or states an explicit boundary.

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?

"Use when evaluating staffing agency pricing or negotiating a travel nurse or locum contract" gives a clear, actionable trigger context. There is no when-not-to-use guidance and no named alternative for related compensation or rate benchmarks, 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