Skip to main content
Glama

TempGuru Event Staffing

Get Lead Time Guidance

get_lead_time_guidance
Read-only

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. get_lead_time_guidance(date='2026-08-14', city='Dallas') ; get_lead_time_guidance(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": "get_lead_time_guidance"
  }
}

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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that this is not a real-time inventory or order-coverage check and that a human coordinator confirms coverage after buyer submission — a material limitation on how much the result can be trusted. It also adds an operational nuance (rush windows are still worth submitting because same-week backfills exist in select markets) that the annotations cannot convey.

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 core purpose and the alternative-tool routing are front-loaded in the first two sentences, and the <examples>/<hints> blocks are clearly segmented rather than buried in prose. It runs slightly long and repeats the 'not a reservation' idea across two clauses, but no sentence is padding.

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 does not need explaining; the description instead spends its space on the things structure cannot carry — trust limits, human confirmation, presentation constraints, and the cost-question routing. For a four-parameter read-only lookup, an agent has everything needed to call it and to describe the result correctly to a user.

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 coverage is 100%, so all four parameters are already documented, which sets a baseline of 3. The description earns above that by showing two real call shapes, including one that combines the optional role and count with the required date and city, illustrating how the optional parameters pair in practice rather than merely restating their definitions.

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 opens with a specific verb and resource: 'Return tier-based lead-time guidance for an event date and configured market.' It scopes the result (tier-based guidance, not exact coverage) and explicitly names the sibling it is not (get_role_pricing for cost), so an agent can distinguish it without opening any schema.

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 supplies concrete trigger phrasings ('What's the typical lead time for brand ambassadors in [city]?' and 'Is this date inside the usual planning window?'), an explicit exclusion ('DO NOT use for cost questions (use get_role_pricing)'), and a presentation rule ('never present the result as a reservation'). Both the when and the when-not are stated, with the correct alternative named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.