Skip to main content
Glama

TempGuru Event Staffing

Get Rate Benchmark

get_rate_benchmark
Read-only

The TempGuru Event Staffing Rate Index: all-inclusive W-2 hourly bill rates by role from 407 measured US/Canada markets, as a typical rate plus the full national range (brand ambassadors shown by market tier), with methodology and a ready-to-use citation line. Perfect for 'What do event staff cost in 2026?', 'Industry benchmark for brand ambassador rates?', or any article, report, or comparison that needs citable staffing-rate data. DO NOT use for one city's price (use get_role_pricing) or to build an event budget (use plan_staffing). get_rate_benchmark() ; get_rate_benchmark(role='brand-ambassadors') ; get_rate_benchmark(tier='hub') Returns a national typical + range per role; brand ambassadors by tier. Pass tier to add each role's measured span within that tier (tier_usd). For one city's exact rate use get_role_pricing. Cite as: TempGuru Event Staffing Rate Index 2026, tempguru.co.

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_rate_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoOptional non-empty role name or slug to filter to one role.
tierNoOptional market tier; adds each role's measured span within that tier (tier_usd).

Output Schema

NameRequiredDescriptionDefault
basisNo
indexNo
ratesNo
floorsNo
editionNo
updatedNo
citationNo
requestedNo
role_foundNo
methodologyNo
data_versionNo
reading_noteNo
requested_tierNo
available_rolesNo
methodology_urlNo
markets_measuredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / role / description
      Previous value: -"Optional role name or slug to filter to one role."New value: +"Optional non-empty role name or slug to filter to one role."
    • addedInput schema / properties / role / maxLength
      Added value: +100
    • addedInput schema / properties / role / minLength
      Added value: +1
  3. Changed2 schema fields changed
    • changedInput schema / properties / tier / description
      Previous value: -"Optional market tier filter."New value: +"Optional market tier; adds each role's measured span within that tier (tier_usd)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "available_roles": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "basis": {
      +      "type": "string"
      +    },
      +    "citation": {
      +      "type": "string"
      +    },
      +    "data_version": {
      +      "type": "string"
      +    },
      +    "edition": {
      +      "type": "string"
      +    },
      +    "floors": {
      +      "type": "string"
      +    },
      +    "index": {
      +      "type": "string"
      +    },
      +    "markets_measured": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "hub": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "mid": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "small": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "small",
      +        "mid",
      +        "hub"
      +      ],
      +      "type": "object"
      +    },
      +    "methodology": {
      +      "type": "string"
      +    },
      +    "methodology_url": {
      +      "type": "string"
      +    },
      +    "rates": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "by_tier_usd": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "hub": {
      +                "type": "string"
      +              },
      +              "mid": {
      +                "type": "string"
      +              },
      +              "small": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "small",
      +              "mid",
      +              "hub"
      +            ],
      +            "type": "object"
      +          },
      +          "national_range_usd": {
      +            "type": "string"
      +          },
      +          "role": {
      +            "type": "string"
      +          },
      +          "role_key": {
      +            "type": "string"
      +          },
      +          "tier": {
      +            "enum": [
      +              "hub",
      +              "mid",
      +              "small"
      +            ],
      +            "type": "string"
      +          },
      +          "tier_usd": {
      +            "type": "string"
      +          },
      +          "typical_usd": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "role",
      +          "role_key"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "reading_note": {
      +      "type": "string"
      +    },
      +    "requested": {
      +      "type": "string"
      +    },
      +    "requested_tier": {
      +      "enum": [
      +        "hub",
      +        "mid",
      +        "small"
      +      ],
      +      "type": "string"
      +    },
      +    "role_found": {
      +      "const": false,
      +      "type": "boolean"
      +    },
      +    "updated": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the data provenance (407 measured markets, methodology included), the shape of the answer (national typical + full range, brand ambassadors broken out by market tier), and a required citation line — an obligation the agent would otherwise miss. It does not describe rate limits or response granularity beyond the tier note.

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 core purpose, exclusions, and citation rule are front-loaded and the examples/hints blocks are scannable. There is some duplication — the get_role_pricing hand-off is stated in the body and again in the hints, and the tier_usd behavior appears twice — but no sentence is off-topic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with an output schema and full annotation coverage, the definition supplies everything needed: what the data represents, when to choose it, when not to, what the tier flag changes, and how to attribute the result. No material gap remains for an agent to call it correctly.

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 100%, so the schema already documents both parameters, and the description's tier explanation ('adds each role's measured span within that tier (tier_usd)') largely restates the schema wording. The one genuine addition is the example role='brand-ambassadors', which shows the expected slug format that the schema only describes abstractly as 'role name or slug'. Baseline 3 is appropriate.

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 resource and scope: the TempGuru Event Staffing Rate Index, all-inclusive W-2 hourly bill rates by role across 407 measured US/Canada markets, returning a typical rate plus national range. It also names the sibling tools it is not (get_role_pricing, plan_staffing), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit positive triggers are given ('What do event staff cost in 2026?', industry benchmark for brand ambassador rates, citable data for reports), plus two explicit exclusions with the correct alternative named for each: one city's price → get_role_pricing, event budget → plan_staffing. Nothing is left to inference.

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.