Skip to main content
Glama
Tempguru-co

TempGuru Event Staffing

Official
by Tempguru-co

Request Quote

request_quote
Read-onlyIdempotent

Convert a saved staffing plan into a TempGuru-hosted review form. The buyer submits their own details directly to request a quote, keeping personal data out of the MCP call.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesSaved non-PII plan reference returned by plan_staffing or save_staffing_plan.
skill_idNoOptional canonical TempGuru skill that assembled the plan.
skill_versionNoOptional version of the TempGuru staffing skill used.
source_platformNoOptional agent/platform attribution, e.g. claude-ai, openclaw, or hermes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesHuman-readable outcome to relay to the buyer.
plan_idYes
form_urlNoPrefilled TempGuru-owned review form. Present only when handoff_ready is true.
next_stepsYesSafe next actions; no agent-side contact collection.
plan_foundYesWhether the supplied non-PII plan_id resolved before expiry.
handoff_readyYestrue when the saved plan resolved and a prefilled buyer form URL was created.
buyer_submission_requiredYesAlways true. The buyer, not the agent, must enter contact details and submit the form.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed20 schema fields changedv1.7.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / attire
      Removed value: -{
      -  "description": "Staff attire requirements",
      -  "type": "string"
      -}
    • removedInput schema / properties / budget_range
      Removed value: -{
      -  "description": "Estimated total budget range if calculated, e.g. '$8,400–$12,600'",
      -  "type": "string"
      -}
    • removedInput schema / properties / city
      Removed value: -{
      -  "description": "City where the event is held",
      -  "type": "string"
      -}
    • removedInput schema / properties / company
      Removed value: -{
      -  "description": "Company or organization name",
      -  "type": "string"
      -}
    • removedInput schema / properties / compliance_notes
      Removed value: -{
      -  "description": "Any compliance flags surfaced by get_compliance_by_state",
      -  "type": "string"
      -}
    • removedInput schema / properties / contact_email
      Removed value: -{
      -  "description": "Contact email address for the quote response",
      -  "format": "email",
      -  "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      -  "type": "string"
      -}
    • removedInput schema / properties / contact_name
      Removed value: -{
      -  "description": "Full name of the contact person",
      -  "type": "string"
      -}
    • removedInput schema / properties / event_dates
      Removed value: -{
      -  "description": "Event dates as a human-readable string, e.g. 'June 15–17, 2026'",
      -  "type": "string"
      -}
    • removedInput schema / properties / event_name
      Removed value: -{
      -  "description": "Name of the event (e.g. 'HIMSS 2026', 'Brand Fest Austin')",
      -  "type": "string"
      -}
    • removedInput schema / properties / event_type
      Removed value: -{
      -  "description": "Event type: trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other",
      -  "type": "string"
      -}
    • addedInput schema / properties / plan_id
      Added value: +{
      +  "description": "Saved non-PII plan reference returned by plan_staffing or save_staffing_plan.",
      +  "maxLength": 12,
      +  "pattern": "^[A-HJ-NP-Z2-9]{12}$",
      +  "type": "string"
      +}
    • removedInput schema / properties / roles
      Removed value: -{
      -  "description": "Roles and headcount needed for the event",
      -  "items": {
      -    "properties": {
      -      "headcount": {
      -        "description": "Number of staff needed",
      -        "exclusiveMinimum": 0,
      -        "maximum": 9007199254740991,
      -        "type": "integer"
      -      },
      -      "role": {
      -        "description": "Staffing role name, e.g. brand-ambassadors, registration-staff",
      -        "type": "string"
      -      },
      -      "shifts": {
      -        "description": "Shift description, e.g. '2 days × 8h'",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "role",
      -      "headcount"
      -    ],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / skill_id
      Added value: +{
      +  "description": "Optional canonical TempGuru skill that assembled the plan.",
      +  "enum": [
      +    "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"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / skill_version
      Added value: +{
      +  "description": "Optional version of the TempGuru staffing skill used.",
      +  "maxLength": 40,
      +  "minLength": 1,
      +  "pattern": "^[0-9]{1,4}\\.[0-9]{1,4}\\.[0-9]{1,4}(?:-[0-9A-Za-z.-]{1,24})?(?:\\+[0-9A-Za-z.-]{1,24})?$",
      +  "type": "string"
      +}
    • addedInput schema / properties / source_platform
      Added value: +{
      +  "description": "Optional agent/platform attribution, e.g. claude-ai, openclaw, or hermes.",
      +  "enum": [
      +    "ai-agent",
      +    "ai-page",
      +    "ai-page-zh",
      +    "baidu-agent",
      +    "chatgpt-app",
      +    "chatgpt-gpt",
      +    "claude-ai",
      +    "claude-code",
      +    "claude-desktop",
      +    "cn-agent",
      +    "copilot-agent",
      +    "coze",
      +    "coze-bot",
      +    "custom-gpt",
      +    "gemini",
      +    "gemini-cli",
      +    "gemini-gem",
      +    "hermes",
      +    "kimi",
      +    "langchain",
      +    "lechat-agent",
      +    "llamaindex",
      +    "manual-test",
      +    "meta-ai",
      +    "mcp-handoff",
      +    "open-webui",
      +    "openai-codex",
      +    "openclaw",
      +    "perplexity-space",
      +    "pi",
      +    "poe-bot",
      +    "postman",
      +    "prime-agent",
      +    "python-client",
      +    "skill",
      +    "team-demo",
      +    "website",
      +    "website-widget",
      +    "zhipu-agent",
      +    "openai-chatgpt",
      +    "openai-agents-sdk",
      +    "openai-mcp",
      +    "cursor",
      +    "cline",
      +    "windsurf",
      +    "perplexity",
      +    "qwen-ecosystem",
      +    "deepseek",
      +    "doubao",
      +    "mcp-client"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / special_requirements
      Removed value: -{
      -  "description": "Any special requirements: language skills, certifications, overnight shifts, etc.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "contact_name",
      -  "contact_email",
      -  "company",
      -  "event_name",
      -  "event_type",
      -  "city",
      -  "event_dates",
      -  "roles"
      -]New value: +[
      +  "plan_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "buyer_submission_required": {
      +      "const": true,
      +      "description": "Always true. The buyer, not the agent, must enter contact details and submit the form.",
      +      "type": "boolean"
      +    },
      +    "form_url": {
      +      "description": "Prefilled TempGuru-owned review form. Present only when handoff_ready is true.",
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "handoff_ready": {
      +      "description": "true when the saved plan resolved and a prefilled buyer form URL was created.",
      +      "type": "boolean"
      +    },
      +    "message": {
      +      "description": "Human-readable outcome to relay to the buyer.",
      +      "type": "string"
      +    },
      +    "next_steps": {
      +      "description": "Safe next actions; no agent-side contact collection.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "plan_found": {
      +      "description": "Whether the supplied non-PII plan_id resolved before expiry.",
      +      "type": "boolean"
      +    },
      +    "plan_id": {
      +      "pattern": "^[A-HJ-NP-Z2-9]{12}$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "handoff_ready",
      +    "buyer_submission_required",
      +    "plan_found",
      +    "plan_id",
      +    "message",
      +    "next_steps"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already carry readOnlyHint, idempotentHint, and destructiveHint, but the description adds meaningful non-obvious behavior: it never transmits contact information, never creates a lead itself, requires the buyer to open and submit the form, and does not reserve or guarantee pricing/availability. There is no contradiction with the annotation object.

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?

The description is dense but front-loaded with the trigger condition and key requirement. It is arguably a little long and contains a couple of repeated privacy-related caveats, but each sentence carries a meaningful operational or safety instruction for an agent.

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 the schema covers all parameters, an output schema exists, and annotations cover the read-only behavior, the description supplies what is left: preconditions, fallback behavior, expiration handling, and the PII boundary. The tool is fully covered from the perspective of an agent deciding whether and how to invoke it.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline applies. The description does reinforce that plan_id must be a saved non-PII plan reference from plan_staffing or save_staffing_plan, but it adds no new meaning for skill_id, skill_version, or source_platform beyond what the schema already documents.

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 names a specific verb and resource: after a buyer asks to proceed, return a TempGuru-owned pre-filled review form for a saved plan_id. It explicitly states the tool does not create a quote reference or CRM lead, which clearly distinguishes its purpose from quote-status or lead-creation tools.

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?

It gives an explicit trigger condition, required input source, and the buyer's required follow-up action. It also gives concrete when-not guidance by saying to give continuation.form_url directly when no plan_id exists, to never collect contact details, and to re-run an expired plan.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tempguru-co/tempguru-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server