Skip to main content
Glama
TempGuru Event Staffing

TempGuru Event Staffing

Official
by Tempguru-co

Check Availability

check_availability
Read-only

Get tier-based lead-time guidance for an event date and city to determine if it falls inside the typical planning window before requesting staff.

Instructions

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. check_availability(date='2026-08-14', city='Dallas') ; check_availability(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6) Even a 'rush' window is worth submitting, same-week backfills exist in select markets.

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": {
      "date": "<date>",
      "city": "<city>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').
dateYesEvent date as YYYY-MM-DD; legacy recognizable dates are still accepted.
roleNoOptional role name or slug to include rate context.
countNoOptional headcount for the event.

Output Schema

NameRequiredDescriptionDefault
cityNo
roleNoRate context when a role was provided; null otherwise.
countNoEcho of the requested headcount.
errorNoPresent when the date could not be parsed.
notesNo
stateNo
in_pastNoTrue when the requested date is already in the past — confirm the date before planning.
messageNoPresent when city_found is false.
city_tierNoMarket tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets.
requestedNoEcho of the unmatched city input.
city_foundYesfalse = city did not match the configured catalog (see message); true = planning guidance below, not confirmed coverage.
event_dateNoNormalized ISO date (YYYY-MM-DD).
role_foundNonull = no role requested; false = the requested role didn't match the catalog (see notes).
suggestionNoClosest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
catalog_matchNo
recommendationNoLead-time guidance, NOT a reservation. Even rush is worth submitting.
role_suggestionNoClosest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
days_until_eventNo
typical_lead_time_hoursNo
coverage_confirmation_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.3
    • removedOutput schema / properties / role_found / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / role_found / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
  2. Changed4 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"
    • changedInput schema / properties / date / description
      Previous value: -"Event date in ISO format (YYYY-MM-DD) or any date string parseable by Date()."New value: +"Event date as YYYY-MM-DD; legacy recognizable dates are still accepted."
    • addedInput schema / properties / date / format
      Added value: +"date"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "catalog_match": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "city": {
      +      "type": "string"
      +    },
      +    "city_found": {
      +      "description": "false = city did not match the configured catalog (see message); true = planning guidance below, not confirmed coverage.",
      +      "type": "boolean"
      +    },
      +    "city_tier": {
      +      "description": "Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets.",
      +      "enum": [
      +        "hub",
      +        "mid",
      +        "small"
      +      ],
      +      "type": "string"
      +    },
      +    "count": {
      +      "anyOf": [
      +        {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Echo of the requested headcount."
      +    },
      +    "coverage_confirmation_required": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "days_until_event": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "error": {
      +      "description": "Present when the date could not be parsed.",
      +      "type": "string"
      +    },
      +    "event_date": {
      +      "description": "Normalized ISO date (YYYY-MM-DD).",
      +      "type": "string"
      +    },
      +    "in_past": {
      +      "description": "True when the requested date is already in the past — confirm the date before planning.",
      +      "type": "boolean"
      +    },
      +    "message": {
      +      "description": "Present when city_found is false.",
      +      "type": "string"
      +    },
      +    "notes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "recommendation": {
      +      "description": "Lead-time guidance, NOT a reservation. Even rush is worth submitting.",
      +      "enum": [
      +        "yes",
      +        "tight",
      +        "rush",
      +        "very-rush"
      +      ],
      +      "type": "string"
      +    },
      +    "requested": {
      +      "description": "Echo of the unmatched city input.",
      +      "type": "string"
      +    },
      +    "role": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "all_inclusive": {
      +              "type": "string"
      +            },
      +            "name": {
      +              "type": "string"
      +            },
      +            "rate_range_usd": {
      +              "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": [
      +            "name",
      +            "rate_range_usd",
      +            "all_inclusive"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Rate context when a role was provided; null otherwise."
      +    },
      +    "role_found": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "null = no role requested; false = the requested role didn't match the catalog (see notes)."
      +    },
      +    "role_suggestion": {
      +      "additionalProperties": false,
      +      "description": "Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply.",
      +      "properties": {
      +        "kind": {
      +          "enum": [
      +            "city",
      +            "role"
      +          ],
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "slug": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "slug",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "state": {
      +      "type": "string"
      +    },
      +    "suggestion": {
      +      "additionalProperties": false,
      +      "description": "Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply.",
      +      "properties": {
      +        "kind": {
      +          "enum": [
      +            "city",
      +            "role"
      +          ],
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "slug": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "slug",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "typical_lead_time_hours": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "city_found"
      +  ],
      +  "type": "object"
      +}
  3. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/no open-world, and the description adds substantive context beyond them: results are tier-based guidance, not inventory; a human coordinator confirms coverage after submission; output must not be framed as a reservation. That is exactly the operational nuance an agent needs to relay results honestly.

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?

Purpose and the critical negative constraint are front-loaded, then examples and hints are segregated into tagged blocks. Slightly dense — the 'not a real-time inventory' point is restated in three ways (inventory, coordinator confirmation, not a reservation) — but each restatement covers a distinct failure mode.

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-shape need not be described, and the remaining gaps an agent would care about (human follow-up step, cost-tool routing, rush-window edge case, display constraints) are all covered. Nothing needed to call or interpret this tool 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 description coverage is 100%, so all four params are self-documenting and the baseline would be 3. The description adds marginal value by showing realistic combinations of the optional role and count alongside required date/city, and by framing city as a 'configured market' (i.e., supported-market constrained) rather than free-form geography.

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 first sentence names a specific verb and resource ('Return tier-based lead-time guidance') plus its scope (event date + configured market). It immediately rules out what it is not ('not a real-time inventory or order-coverage check'), which separates it from order/quote siblings like request_quote and get_quote_status.

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 trigger questions ('What's the typical lead time for brand ambassadors in [city]?'), an explicit exclusion with a redirect ('DO NOT use for cost questions (use get_role_pricing)'), and a presentation constraint ('never present the result as a reservation'). The hints block also tells the agent to still submit rush windows, covering the edge case where an agent might otherwise decline.

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