TempGuru Event Staffing

Get Rate Benchmark (Rate Index)

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`role`	No	Optional non-empty role name or slug to filter to one role.
`tier`	No	Optional market tier; adds each role's measured span within that tier (tier_usd).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`basis`	No
`index`	No
`rates`	No
`floors`	No
`edition`	No
`updated`	No
`citation`	No
`requested`	No
`role_found`	No
`methodology`	No
`data_version`	No
`reading_note`	No
`requested_tier`	No
`available_roles`	No
`methodology_url`	No
`markets_measured`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 29, 2026

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"

Changed3 schema fields changedJul 17, 2026
- 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
```

Changed2 schema fields changedJul 7, 2026

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

AddedJun 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds meaningful behavioral details beyond that: it returns a national typical plus range, handles brand ambassadors by market tier, and describes the optional tier parameter as adding 'tier_usd' data for each role.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is more detailed than average, but every sentence contributes: scope, data source, return value, example use cases, exclusions, citation, and parameter hints are all covered. It is front-loaded with the core result and the guidance to use alternative tools.

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 tool with two optional parameters, an output schema, and clear annotation coverage, this description is complete. It covers the dataset, measurement scope, tier handling, citation format, and appropriate alternatives. An agent can confidently decide when to invoke this tool and understand the shape of the result before even opening the output schema.

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

Parameters4/5

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

Schema coverage is 100%, so parameter basics are already documented. The description adds extra value by explaining what the tier parameter actually does ('adds each role's measured span within that tier (tier_usd)') and by showing concrete example calls with different parameter combinations, which helps an agent understand how to pass arguments correctly.

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 clearly identifies the resource (TempGuru Event Staffing Rate Index) and the specific output: all-inclusive W-2 hourly bill rates by role from 407 markets, with a typical rate plus the national range. It also explicitly distinguishes itself from related tools like get_role_pricing and plan_staffing by stating what the tool is NOT for.

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?

Usage guidance is explicit and actionable. It provides example queries, states when to use the tool ('What do event staff cost in 2026?', 'Industry benchmark'), and gives clear exclusions: do not use for one city's price (use get_role_pricing) or to build a budget (use plan_staffing).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TempGuru Event Staffing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.