Skip to main content
Glama

TempGuru Event Staffing

Get Role Pricing

get_role_pricing
Read-only

Get the all-inclusive hourly rate range for a specific role in a specific city. Perfect for 'What does it cost to hire brand ambassadors in [city]?', 'How much are registration workers in [city]?', or 'What's the rate for ushers at a [city] stadium event?' questions. All rates include W-2 worker pay, workers comp, general liability, and payroll taxes. DO NOT use for availability or dates (use get_lead_time_guidance) and never present the range as a binding quote. For a multi-role budget, use plan_staffing. get_role_pricing(role='Brand Ambassadors', city='Boston') ; get_role_pricing(role='registration-staff', city='nashville-event-staffing') Role and city accept names or slugs. Brand Ambassadors floor at $40/hour in every market.

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": {
      "role": "<role>",
      "city": "<city>"
    },
    "name": "get_role_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').
roleYesRole name (e.g., 'Brand Ambassadors') or slug (e.g., 'brand-ambassadors').

Output Schema

NameRequiredDescriptionDefault
cityNo
noteNo
roleNo
errorNo
stateNo
currencyNo
city_tierNoMarket tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets.
requestedNoEcho of the unmatched input.
role_noteNoCaveat about the resolved role (e.g. 'security' maps to unarmed Crowd Control, not licensed security).
role_slugNo
city_foundNoPresent (false) only when the city didn't match.
role_foundNoPresent (false) only when the role didn't match.
suggestionNoClosest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
all_inclusiveNo
pricing_notesNo
available_rolesNoThe valid role catalog, returned when the role didn't match.
tier_definitionNo
fallback_pricingNoAll-tier pricing shown when the city didn't match.
hourly_range_lowNo
hourly_range_highNo
all_tiers_for_contextNoRate bands across all three market tiers for context.

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. Changed1 schema field changed
    • changedOutput schema / properties / city_tier / description
      Previous value: -"Market tier: hub = 25 major metros, mid = 129 secondary markets, small = 191 tertiary markets."New value: +"Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets."
  3. Changed2 schema fields changed
    • addedOutput schema / properties / role_note
      Added value: +{
      +  "description": "Caveat about the resolved role (e.g. 'security' maps to unarmed Crowd Control, not licensed security).",
      +  "type": "string"
      +}
    • changedOutput schema / properties / suggestion / description
      Previous value: -"Closest known city/role for a miss; retry with this slug."New value: +"Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply."
  4. Changed1 schema field changed
    • addedOutput schema / properties / suggestion
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Closest known city/role for a miss; retry with this slug.",
      +  "properties": {
      +    "kind": {
      +      "enum": [
      +        "city",
      +        "role"
      +      ],
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "slug": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "slug",
      +    "name"
      +  ],
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "all_inclusive": {
      +      "type": "string"
      +    },
      +    "all_tiers_for_context": {
      +      "additionalProperties": false,
      +      "description": "Rate bands across all three market tiers for context.",
      +      "properties": {
      +        "hub": {
      +          "additionalProperties": false,
      +          "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
      +          "properties": {
      +            "high": {
      +              "description": "Upper end of the hourly rate range.",
      +              "type": "number"
      +            },
      +            "low": {
      +              "description": "Lower end of the hourly rate range.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high"
      +          ],
      +          "type": "object"
      +        },
      +        "mid": {
      +          "additionalProperties": false,
      +          "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
      +          "properties": {
      +            "high": {
      +              "description": "Upper end of the hourly rate range.",
      +              "type": "number"
      +            },
      +            "low": {
      +              "description": "Lower end of the hourly rate range.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high"
      +          ],
      +          "type": "object"
      +        },
      +        "small": {
      +          "additionalProperties": false,
      +          "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
      +          "properties": {
      +            "high": {
      +              "description": "Upper end of the hourly rate range.",
      +              "type": "number"
      +            },
      +            "low": {
      +              "description": "Lower end of the hourly rate range.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "small",
      +        "mid",
      +        "hub"
      +      ],
      +      "type": "object"
      +    },
      +    "available_roles": {
      +      "description": "The valid role catalog, returned when the role didn't match.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "city": {
      +      "type": "string"
      +    },
      +    "city_found": {
      +      "const": false,
      +      "description": "Present (false) only when the city didn't match.",
      +      "type": "boolean"
      +    },
      +    "city_tier": {
      +      "description": "Market tier: hub = 25 major metros, mid = 129 secondary markets, small = 191 tertiary markets.",
      +      "enum": [
      +        "hub",
      +        "mid",
      +        "small"
      +      ],
      +      "type": "string"
      +    },
      +    "currency": {
      +      "enum": [
      +        "USD",
      +        "CAD"
      +      ],
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "fallback_pricing": {
      +      "additionalProperties": false,
      +      "description": "All-tier pricing shown when the city didn't match.",
      +      "properties": {
      +        "hub": {
      +          "additionalProperties": false,
      +          "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
      +          "properties": {
      +            "high": {
      +              "description": "Upper end of the hourly rate range.",
      +              "type": "number"
      +            },
      +            "low": {
      +              "description": "Lower end of the hourly rate range.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high"
      +          ],
      +          "type": "object"
      +        },
      +        "mid": {
      +          "additionalProperties": false,
      +          "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
      +          "properties": {
      +            "high": {
      +              "description": "Upper end of the hourly rate range.",
      +              "type": "number"
      +            },
      +            "low": {
      +              "description": "Lower end of the hourly rate range.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high"
      +          ],
      +          "type": "object"
      +        },
      +        "small": {
      +          "additionalProperties": false,
      +          "description": "All-inclusive hourly rate band (worker pay + payroll taxes + workers comp + liability).",
      +          "properties": {
      +            "high": {
      +              "description": "Upper end of the hourly rate range.",
      +              "type": "number"
      +            },
      +            "low": {
      +              "description": "Lower end of the hourly rate range.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "low",
      +            "high"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "small",
      +        "mid",
      +        "hub"
      +      ],
      +      "type": "object"
      +    },
      +    "hourly_range_high": {
      +      "type": "number"
      +    },
      +    "hourly_range_low": {
      +      "type": "number"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "pricing_notes": {
      +      "type": "string"
      +    },
      +    "requested": {
      +      "description": "Echo of the unmatched input.",
      +      "type": "string"
      +    },
      +    "role": {
      +      "type": "string"
      +    },
      +    "role_found": {
      +      "const": false,
      +      "description": "Present (false) only when the role didn't match.",
      +      "type": "boolean"
      +    },
      +    "role_slug": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "type": "string"
      +    },
      +    "tier_definition": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/no destructive behavior; the description adds real value beyond them by stating what the rate includes (W-2 pay, workers comp, general liability, payroll taxes) and warning that the range is not a binding quote. The one gap is that it doesn't characterize output shape or market coverage limits, though the $40 floor hint partially addresses the latter.

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-loaded with the core sentence, then exclusions, then examples and hints, which is a sensible order. It runs long and partly duplicates schema text (the slug formats), but every section still carries routing or pricing information.

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?

An output schema exists, so return values need not be explained, and the description covers the call constraints, pricing caveats, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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% and the schema already explains name-or-slug acceptance for both params, so the description largely restates it. Marginal gain comes from the concrete paired examples (mixed name/slug forms), which show that a name and a slug can be combined in one call.

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?

Names a specific verb and resource ('Get the all-inclusive hourly rate range') and scopes it to a role within a city, which an agent can distinguish at a glance from get_rate_benchmark or plan_staffing. It even names the question shapes the tool answers.

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?

Gives explicit when-to-use examples plus hard exclusions: do not use for availability or dates (route to get_lead_time_guidance) and do not present the range as a binding quote. It also names plan_staffing as the alternative for multi-role budgets, so nothing about routing 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.