Skip to main content
Glama

TempGuru Event Staffing

by co.tempguru

Get Roles

get_roles
Read-only

List event staffing roles TempGuru provides, with descriptions and skill tiers. Perfect for 'What kinds of event workers can I hire?', 'What roles do you staff for trade shows / festivals / corporate events?', or 'Do you have brand ambassadors?' questions. DO NOT use for what a role costs, use get_role_pricing with a city. get_roles() Returned slugs (brand-ambassadors, registration-staff, team-leads) are the exact values the other tools accept.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rolesYes
totalYes

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint. Description adds that returned slugs are the exact values other tools accept, which is useful context beyond annotations.

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?

Two sentences plus <examples> and <hints>. Front-loaded with purpose, then usage guidance and practical hints. Zero waste.

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?

Given no parameters, annotations covering safety, and output schema present, the description fully equips an agent to select and invoke this tool correctly.

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

Parameters5/5

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

Input schema has 0 parameters and coverage is 100%, so description need not add param details. No gaps.

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?

Description clearly states 'List event staffing roles TempGuru provides, with descriptions and skill tiers.' It gives explicit question examples ('What kinds of event workers can I hire?') and differentiates from get_role_pricing.

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?

Explicitly says 'DO NOT use for what a role costs, use get_role_pricing with a city.' Also hints that returned slugs are used by other tools.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose with explicit do-not-use cross-references. Pricing tools (get_rate_benchmark vs get_role_pricing) are carefully separated, and plan_staffing vs check_availability serve different granularity needs.

Naming Consistency5/5

All tools use a consistent verb_noun snake_case pattern (get_cities, plan_staffing, request_quote). The verbs are simple and descriptive, with no mixed casing or stylistic inconsistencies.

Tool Count5/5

12 tools is well-scoped for an event staffing domain covering availability, pricing, roles, compliance, planning, persistence, and quote workflows. Each tool earns its place without redundancy.

Completeness4/5

The workflow is well-covered: plan_staffing creates plans, save/get manage persistence, request_quote hands off to a form, and get_quote_status tracks references. Minor gaps exist like lack of plan update/delete and quote status being a stub, but core operations are complete.

Resources