co.tempguru/event-staffing

Est-ce que co.tempguru/event-staffing est sûr ?

Au dernier audit MCP Hub, le serveur MCP « co.tempguru/event-staffing » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• check_availability≈ 1224 tokens

  Return tier-based lead-time guidance for an event date and configured market. Use for 'What's the typical lead time for brand ambassadors in [city]?' or 'Is this date inside the usual planning window?'. This is not a real-time inventory or order-coverage check: a TempGuru coordinator confirms coverage and final lead time for the specific order after buyer submission. DO NOT use for cost questions (use get_role_pricing) and never present the result as a reservation. <examples>check_availability(date='2026-08-14', city='Dallas') ; check_availability(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6)</examples> <hints>Even a 'rush' window is worth submitting, same-week backfills exist in select markets.</hints>

  Paramètres, retour & exemple (4)

  Paramètres

  • city · string · requis
    City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').
  • date · string · requis
    Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
  • role · string · optionnel
    Optional role name or slug to include rate context.
  • count · integer · optionnel
    Optional headcount for the event.

  Exemple d'appel

  {"name": "check_availability", "arguments": {"city": "texte", "date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"city": "texte", "role": "texte", "count": "texte", "error": "texte", "notes": [], "state": "texte", "in_past": true, "message": "texte", "city_tier": "hub", "requested": "texte", "city_found": true, "event_date": "texte"}}

• get_cities≈ 1253 tokens

  List configured market entries by tier, or match one city. Catalog presence is not availability or order coverage; check_availability gives tier-based lead-time guidance only, and a coordinator confirms each order after buyer submission. Use for 'What markets are configured in [state]?', 'Is [city] in the catalog?', or 'Which Canadian markets are listed?'. For 'Do you cover [city]?' pass city='[name]', report the catalog match or suggestion, and preserve the coordinator-confirmation caveat. Use get_role_pricing for rates, check_availability for dates, or plan_staffing for a full plan. <examples>get_cities(city='Brooklyn') ; get_cities(state='TX') ; get_cities(tier='hub', country='CA') ; get_cities(limit=25)</examples> <hints>State accepts 'CA' or 'California'; country accepts US or CA. City resolves nicknames and boroughs. Unfiltered results are capped; use filters or limit. Configured entries are planning data; the public coverage claim is 300+ U.S. and Canadian markets.</hints>

  Paramètres, retour & exemple (5)

  Paramètres

  • city · string · optionnel
    Optional single-city catalog match (nickname/borough aware). Returns catalog_match plus a suggestion; never a coverage promise.
  • tier · string · optionnel · hub | mid | small
    Optional filter to one tier only.
  • limit · integer · optionnel
    Optional cap on the number of cities returned (full counts still in total/tier_breakdown).
  • state · string · optionnel
    Optional 2-letter state code (e.g., 'CA') or full state name.
  • country · string · optionnel
    Optional country filter: 'US' or 'CA'.

  Exemple d'appel

  {"name": "get_cities", "arguments": {"city": "texte", "tier": "hub", "limit": 1, "state": "texte", "country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"city": "texte", "note": "texte", "total": 1, "cities": [], "message": "texte", "returned": 1, "requested": "texte", "suggestion": {}, "catalog_check": true, "catalog_match": true, "tier_breakdown": {}, "catalog_qualification": "texte"}}

• get_compliance_by_state≈ 862 tokens

  Get the event staffing compliance summary for a US state. Returns minimum wage, overtime rules, and state-specific quirks. Perfect for 'What are the W-2 vs 1099 rules for event workers in [state]?', 'What's the minimum wage for event staff in [state]?', or 'Are there compliance gotchas for hiring event workers in [state]?' questions. NOT legal advice, consult employment counsel for binding interpretation. DO NOT use for rates (use get_role_pricing). <examples>get_compliance_by_state(state='CA') ; get_compliance_by_state(state='Tennessee')</examples> <hints>Daily-overtime states (CA, AK, NV, CO) change shift budgeting, flag them in any plan.</hints>

  Paramètres, retour & exemple (1)

  Paramètres

  • state · string · requis
    Two-letter state code (e.g., 'CA') or full state name (e.g., 'California').

  Exemple d'appel

  {"name": "get_compliance_by_state", "arguments": {"state": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"state": "texte", "w2_note": "texte", "requested": "texte", "state_abbr": "texte", "state_found": true, "w2_required": true, "data_version": "texte", "min_wage_usd": 1, "unique_rules": [], "citation_note": "texte", "currency_note": "texte", "min_wage_as_of": "texte"}}

• get_plan≈ 1167 tokens

  Restore a complete non-PII staffing plan created by plan_staffing or save_staffing_plan within the last 30 days. Use when a buyer starts a new conversation, changes agent platforms, or wants to continue a saved plan before requesting a quote. DO NOT guess or enumerate plan IDs; use only the 12-character plan_id the user, plan_staffing, or save_staffing_plan supplied. <examples>get_plan(plan_id='ABCDEFGH2345')</examples> <hints>A not-found result means the plan expired, storage was unavailable, or the ID is wrong; re-run plan_staffing. Review the restored plan with the user before request_quote.</hints>

  Paramètres, retour & exemple (1)

  Paramètres

  • plan_id · string · requis
    12-character lookalike-free plan reference returned by plan_staffing or save_staffing_plan.

  Exemple d'appel

  {"name": "get_plan", "arguments": {"plan_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "plan_id": "texte", "snapshot": {}, "next_steps": [], "offer_note": "texte", "plan_found": true, "continuation": {}}}

• get_policies≈ 757 tokens

  Get TempGuru's published booking and procurement policies, plus any currently published public offer. Use for real booking questions that otherwise require an email. Values not supported by canonical copy are explicitly marked confirm_with_coordinator with TODO-for-Megan; never infer a missing number. <examples>get_policies() ; get_policies(topic='payment-terms') ; get_policies(topic='coi-additional-insured')</examples> <hints>Choose an advertised topic to return one policy. Narrow lexical aliases remain accepted, and unknown topics return the current available-topic list. This is an operational summary, not a contract.</hints>

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · optionnel · minimum-booking-hours | cancellation-rescheduling | no-show-backfill | coi-additional-insured | payment-terms | background-checks | order-confirmation | quote-response
    Optional canonical policy topic. Choose an advertised enum value; omit for all policies or a broader question.

  Exemple d'appel

  {"name": "get_policies", "arguments": {"topic": "minimum-booking-hours"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"scope": "texte", "status": "policies", "message": "texte", "updated": "texte", "policies": [], "requested": "texte", "disclaimer": "texte", "data_version": "texte", "policy_found": true, "todo_for_megan": [], "available_topics": []}}

• get_quote_status≈ 439 tokens

  Check whether a TempGuru quote request reference was received by the CRM or durably queued. Use only after the buyer personally submitted a TempGuru website form and received a TG reference, or for a historical reference. The authless MCP request_quote handoff does not create a reference. This v1 status stub reports received/queued only; it does not yet expose quote_sent or won. <examples>get_quote_status(reference='TG-ABC234')</examples> <hints>Status records are retained for 90 days. A not-found result does not prove the CRM lead is absent; follow up with the reference at megan@tempguru.co.</hints>

  Paramètres, retour & exemple (1)

  Paramètres

  • reference · string · requis
    TG reference returned after the buyer submits the TempGuru website form, e.g. TG-ABC234.

  Exemple d'appel

  {"name": "get_quote_status", "arguments": {"reference": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "received", "channel": "mcp", "message": "texte", "deal_name": "texte", "follow_up": "texte", "reference": "texte", "created_at": "texte", "quote_found": true}}

• get_rate_benchmark≈ 801 tokens

  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). <examples>get_rate_benchmark() ; get_rate_benchmark(role='brand-ambassadors') ; get_rate_benchmark(tier='hub')</examples> <hints>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.</hints>

  Paramètres, retour & exemple (2)

  Paramètres

  • role · string · optionnel
    Optional non-empty role name or slug to filter to one role.
  • tier · string · optionnel · hub | mid | small
    Optional market tier; adds each role's measured span within that tier (tier_usd).

  Exemple d'appel

  {"name": "get_rate_benchmark", "arguments": {"role": "texte", "tier": "hub"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"basis": "texte", "index": "texte", "rates": [], "floors": "texte", "edition": "texte", "updated": "texte", "citation": "texte", "requested": "texte", "role_found": true, "methodology": "texte", "data_version": "texte", "reading_note": "texte"}}

• get_role_pricing≈ 1451 tokens

  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 check_availability) and never present the range as a binding quote. For a multi-role budget, use plan_staffing. <examples>get_role_pricing(role='Brand Ambassadors', city='Boston') ; get_role_pricing(role='registration-staff', city='nashville-event-staffing')</examples> <hints>Role and city accept names or slugs. Brand Ambassadors floor at $40/hour in every market.</hints>

  Paramètres, retour & exemple (2)

  Paramètres

  • city · string · requis
    City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').
  • role · string · requis
    Role name (e.g., 'Brand Ambassadors') or slug (e.g., 'brand-ambassadors').

  Exemple d'appel

  {"name": "get_role_pricing", "arguments": {"city": "texte", "role": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"city": "texte", "note": "texte", "role": "texte", "error": "texte", "state": "texte", "currency": "USD", "city_tier": "hub", "requested": "texte", "role_note": "texte", "role_slug": "texte", "city_found": true, "role_found": true}}

• get_roles≈ 415 tokens

  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. <examples>get_roles()</examples> <hints>Returned slugs (brand-ambassadors, registration-staff, team-leads) are the exact values the other tools accept.</hints>

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_roles", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"roles": [], "total": 1}}

• plan_staffing≈ 2822 tokens

  CALL THIS FIRST for event staffing requests. Returns a configured-market catalog match, role-level W-2 rate math, estimated totals, tier-based lead-time guidance, and state compliance flags from the event's city, date, roles, and headcount. It does not confirm order coverage or live inventory; a coordinator does that after buyer submission. Use granular tools only for a single rate, date, or state fact. A complete plan may save a non-contact snapshot for 30 days and return plan_id plus continuation. If it returns no plan_id and the buyer needs persistence, call save_staffing_plan once; never save a plan that already has an ID. This tool never accepts or submits contact details, reserves staff, or creates a quote request. Omit roles for the catalog and a suggested mix. Treat totals as planning estimates, not quotes. Branch on status: plan, needs_roles, roles_not_found, or city_not_found; confirm suggestions rather than auto-applying them.

  Paramètres, retour & exemple (6)

  Paramètres

  • city · string · requis
    Event city, name or slug (e.g., 'Chicago').
  • roles · array · optionnel
    Roles and headcount. Omit to receive the role catalog and a suggested mix.
  • attendees · integer · optionnel
    Expected attendee count.
  • event_date · string · optionnel
    Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
  • event_type · string · optionnel · trade-show | conference | festival | concert | sporting-event | corporate | brand-activation | other
    trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.
  • description · string · optionnel
    Optional free-text event description, echoed into the plan.

  Exemple d'appel

  {"name": "plan_staffing", "arguments": {"city": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tip": "texte", "event": {}, "status": "plan", "message": "texte", "plan_id": "texte", "lead_time": "texte", "compliance": "texte", "next_steps": [], "offer_note": "texte", "plan_lines": [], "suggestion": {}, "continuation": {}}}

• request_quote≈ 946 tokens

  Use only after the buyer reviews a staffing plan and asks to proceed. Requires the saved non-PII plan_id from plan_staffing or save_staffing_plan and returns a prefilled TempGuru-owned review form. This tool never accepts or transmits names, email, phone, company, or other contact details and never creates a CRM lead or quote reference. The buyer must open form_url, review the plan, enter their own details, and submit it; only that submission creates a lead. This is not a reservation and does not guarantee pricing or availability. If a complete plan has continuation.form_url but no plan_id, give that URL directly instead. Never collect contact details for an MCP call; re-run an expired plan.

  Paramètres, retour & exemple (4)

  Paramètres

  • plan_id · string · requis
    Saved non-PII plan reference returned by plan_staffing or save_staffing_plan.
  • skill_id · string · optionnel · event-staffing-ordering | event-staffing-compliance | staffing-plan-from-event-brief | urgent-event-backfill | staffing-agency-partner-growth | multi-city-activation-planner | event-staffing-procurement | tempguru-pro-operations
    Optional canonical TempGuru skill that assembled the plan.
  • skill_version · string · optionnel
    Optional version of the TempGuru staffing skill used.
  • source_platform · string · optionnel · ai-agent | ai-page | ai-page-zh | baidu-agent | chatgpt-app | chatgpt-gpt | claude-ai | claude-code
    Optional agent/platform attribution, e.g. claude-ai, openclaw, or hermes.

  Exemple d'appel

  {"name": "request_quote", "arguments": {"plan_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "plan_id": "texte", "form_url": "texte", "next_steps": [], "plan_found": true, "handoff_ready": true, "buyer_submission_required": true}}

• save_staffing_plan≈ 1253 tokens

  Explicitly save a complete non-contact staffing plan for 30 days so it can be shared, resumed, or linked to a later quote request. Use only when plan_staffing returned plan_complete:true without a plan_id and the user needs persistence. Never call this tool when plan_staffing already returned a plan_id. Provide the same confirmed city, date, event type, attendees, roles, headcount, hours, and days; the server recomputes rates, totals, lead time, and compliance before saving and does not accept caller-supplied pricing or totals. This does not reserve staff, submit contact details, or request a quote. <hints>Branch on status: saved is the only outcome with a durable plan_id; plan_incomplete requires revising the inputs; for rate_limited or storage_unavailable, give the buyer continuation.form_url directly because request_quote requires a saved plan_id.</hints>

  Paramètres, retour & exemple (5)

  Paramètres

  • city · string · requis
    Event city, name or slug (e.g. Chicago).
  • roles · array · requis
    Confirmed roles, headcount, hours, and days to recompute and save.
  • attendees · integer · optionnel
    Expected attendee count.
  • event_date · string · optionnel
    Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
  • event_type · string · optionnel · trade-show | conference | festival | concert | sporting-event | corporate | brand-activation | other
    trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.

  Exemple d'appel

  {"name": "save_staffing_plan", "arguments": {"city": "texte", "roles": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "saved", "message": "texte", "plan_id": "texte", "created_at": "texte", "expires_at": "texte", "plan_status": "plan", "continuation": {}, "next_actions": [], "resource_uri": "texte", "schema_version": "texte", "quote_readiness": "texte", "retry_after_seconds": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.tempguru.co/mcp