Loading ToolBench
MCP server for W-2 event staffing planning across 300+ U.S. and Canadian markets, backed by 5,000+ events and 100,000+ completed shifts, with coordinator-confirmed availability per order.
TempGuru MCP demonstrates solid tool design with clear naming conventions (verb_noun pattern: plan_staffing, get_plan, check_availability), comprehensive parameter descriptions, and well-structured schemas. All 12 tools have descriptions (avg ~120 chars) and typed input schemas. However, output schemas are not documented in the source code provided, and error handling guidance is minimal. Tool composition is strong, tools chain logically (plan_staffing → save_staffing_plan → get_plan → request_quote). Parameter descriptions are detailed with context (e.g., 'Event date in ISO format YYYY-MM-DD', 'Two-letter state code (CA) or full name'). No security issues detected (no credentials in params). Main gaps: missing output schema documentation and limited error recovery guidance.
Tier-based lead-time guidance for a configured city/date, optionally with role and headcount; not an inventory or order-coverage check.
List configured market entries or match one city. Catalog membership is not confirmed order coverage or live inventory.
Minimum wage, overtime rules, and state-specific event-staffing compliance quirks.
Restore a complete non-PII staffing plan saved within the last 30 days.
Published booking and procurement policies, with unsupported values explicitly deferred to a coordinator.
Check a TG reference returned after a buyer-submitted website form, including historical references.
Output schemas not documented in source code. LLMs cannot plan downstream tool calls or extract required fields without knowing response structure.
Error handling and recovery guidance absent. Tools do not indicate what LLM should do on failure (retry, ask user, abort). E.g., plan_staffing may fail if city/date invalid, but no guidance provided.
get_roles and get_policies have minimal descriptions (70-75 chars). Descriptions should explain WHEN to call these tools and what structure they reveal. E.g., 'Call first to discover available roles before planning staffing.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | A | 82 | 2026-07-28+ | v2 |
The TempGuru Event Staffing Rate Index: full benchmark table of all-inclusive W-2 hourly rates by role (typical + national range; Brand Ambassadors by tier), with methodology and citation line.
All-inclusive hourly rate range for a specific role in a specific city.
List all event staffing roles with descriptions and skill tiers.
Planner meta-tool, call first. Turns an event shape into a complete plan and may save a 30-day non-PII snapshot for plan_id continuation. Non-destructive, but not read-only.
Restore a saved non-PII plan and return a prefilled TempGuru buyer form. Read-only: never accepts contact data or creates a lead; the buyer personally submits the form.
Explicitly save a complete plan as a 30-day non-PII artifact after the server recomputes rates and totals from bounded event inputs. Use only when the plan has no plan_id; never duplicate a plan_staffing autosave.
Destructive/write tools (plan_staffing, save_staffing_plan) lack confirmation or dry-run support. Agents may accidentally overwrite plans without explicit user approval.
Parameter 'topic' in get_policies is optional but no guidance on valid values. Should enumerate topics (e.g., 'payment-terms', 'cancellation', 'insurance') or link to discovery tool.