Skip to main content
Glama
TempGuru Event Staffing

TempGuru Event Staffing

Official
by Tempguru-co

Plan Staffing

plan_staffing

Build an event staffing plan with role catalog matches, W-2 rate estimates, totals, lead-time guidance, and state compliance flags from city, date, roles, and headcount.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
cityYesEvent city, name or slug (e.g., 'Chicago').
rolesNoRoles and headcount. Omit to receive the role catalog and a suggested mix.
attendeesNoExpected attendee count.
event_dateNoEvent date as YYYY-MM-DD; legacy recognizable dates are still accepted.
event_typeNotrade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.
descriptionNoOptional free-text event description, echoed into the plan.

Output Schema

NameRequiredDescriptionDefault
tipNo
eventNo
statusYesDiscriminator. Branch on this before reading the rest.
messageNo
plan_idNoComplete plans only. Non-PII plan reference retained for 30 days when Redis persistence succeeds.
lead_timeNo
complianceNo
next_stepsNo
plan_linesNo
suggestionNoClosest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
continuationNoComplete plans only. Prefilled website handoff; may be present without plan_id when storage fails open.
plan_completeNostatus:plan only. false = one or more requested roles could not be priced and are EXCLUDED from all totals (see unpriced_roles) — resolve them and re-plan before presenting a budget or quoting.
requested_cityNo
staffing_notesNo
unpriced_rolesNostatus:plan with plan_complete:false — the requested lines missing from every total.
available_rolesNo
requested_rolesNo
unresolved_rolesNo
estimated_total_rangeNo
overtime_adjusted_total_rangeNoPresent (non-null) only when daily/weekly OT (or a double-time band) applies to the schedule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.7.3
    • changedOutput schema / properties / compliance / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "citation_note": {
      -        "type": "string"
      -      },
      -      "currency_note": {
      -        "type": "string"
      -      },
      -      "data_current_as_of": {
      -        "description": "Date the jurisdiction dataset was last verified (YYYY-MM-DD).",
      -        "type": "string"
      -      },
      -      "data_version": {
      -        "description": "Version identifier for the jurisdiction dataset used by the plan.",
      -        "type": "string"
      -      },
      -      "jurisdiction": {
      -        "description": "US state or Canadian province the rules below belong to.",
      -        "type": "string"
      -      },
      -      "min_wage_as_of": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "Effective date of the stored wage floor; null when no wage is stored."
      -      },
      -      "min_wage_source": {
      -        "anyOf": [
      -          {
      -            "format": "uri",
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "Authoritative wage source; null for Canadian plans where the coordinator confirms the floor."
      -      },
      -      "min_wage_usd": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "US states only; null for Canadian provinces (coordinator confirms provincial wage floors)."
      -      },
      -      "note": {
      -        "type": "string"
      -      },
      -      "overtime_daily_hours": {
      -        "anyOf": [
      -          {
      -            "maximum": 9007199254740991,
      -            "minimum": -9007199254740991,
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "overtime_weekly_hours": {
      -        "anyOf": [
      -          {
      -            "maximum": 9007199254740991,
      -            "minimum": -9007199254740991,
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "unique_rules": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      }
      -    },
      -    "required": [
      -      "jurisdiction",
      -      "min_wage_usd",
      -      "overtime_weekly_hours",
      -      "overtime_daily_hours",
      -      "unique_rules",
      -      "data_version",
      -      "data_current_as_of",
      -      "min_wage_as_of",
      -      "min_wage_source",
      -      "currency_note",
      -      "citation_note",
      -      "note"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "citation_note": {
      +        "type": "string"
      +      },
      +      "currency_note": {
      +        "type": "string"
      +      },
      +      "data_current_as_of": {
      +        "description": "Date the jurisdiction dataset was last verified (YYYY-MM-DD).",
      +        "type": "string"
      +      },
      +      "data_version": {
      +        "description": "Version identifier for the jurisdiction dataset used by the plan.",
      +        "type": "string"
      +      },
      +      "jurisdiction": {
      +        "description": "US state or Canadian province the rules below belong to.",
      +        "type": "string"
      +      },
      +      "min_wage_as_of": {
      +        "description": "Effective date of the stored wage floor; null when no wage is stored.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "min_wage_source": {
      +        "anyOf": [
      +          {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Authoritative wage source; null for Canadian plans where the coordinator confirms the floor."
      +      },
      +      "min_wage_usd": {
      +        "description": "US states only; null for Canadian provinces (coordinator confirms provincial wage floors).",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "note": {
      +        "type": "string"
      +      },
      +      "overtime_daily_hours": {
      +        "anyOf": [
      +          {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "overtime_weekly_hours": {
      +        "anyOf": [
      +          {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "unique_rules": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "jurisdiction",
      +      "min_wage_usd",
      +      "overtime_weekly_hours",
      +      "overtime_daily_hours",
      +      "unique_rules",
      +      "data_version",
      +      "data_current_as_of",
      +      "min_wage_as_of",
      +      "min_wage_source",
      +      "currency_note",
      +      "citation_note",
      +      "note"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / event / properties / attendees / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / event / properties / attendees / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / event / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / event / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / event / properties / event_date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / event / properties / event_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / event / properties / event_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / event / properties / event_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / offer_note
      Removed value: -{
      -  "description": "Published first-order offer note. Totals remain undiscounted planning estimates.",
      -  "type": "string"
      -}
  2. Addedv1.7.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, closed-world tool; the description explains why (it may persist a non-contact 30-day snapshot and return a plan_id) and what it explicitly will not do: accept contact details, reserve staff, or create a quote request. It also sets the interpretation boundary for outputs (totals are planning estimates, not quotes) and states that live inventory/coverage is confirmed by a human coordinator — context 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?

Front-loaded with the imperative call-to-action and ordered sensibly: what it returns, what it excludes, follow-up save rule, then status branching. It runs long and spends two separate sentences on negative disclosures (no coverage/inventory, no contacts/reservations/quotes) that could be consolidated, but nearly every sentence carries actionable information for a workflow-entry tool.

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-value detail is not required, and the description instead covers the parts an agent cannot infer: sequencing across siblings, the 30-day snapshot/plan_id persistence model, the status branches (plan, needs_roles, roles_not_found, city_not_found), and the instruction to confirm rather than auto-apply suggested roles. Nothing needed to invoke or follow up correctly is missing.

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 coverage is 100%, so the schema already documents every field including defaults, bounds, and the enum. The description reinforces only the one non-obvious behavior (omitting roles yields a catalog plus suggested mix) and otherwise describes inputs collectively as "city, date, roles, and headcount." Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource (plan event staffing) and enumerates exactly what the response contains: catalog match, W-2 rate math, estimated totals, lead-time guidance, and compliance flags. It explicitly separates itself from the granular siblings (get_rate_benchmark, get_role_pricing, get_compliance_by_state) and from request_quote/save_staffing_plan, so an agent can route correctly without opening a 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?

"CALL THIS FIRST" gives an explicit entry-point rule, and "Use granular tools only for a single rate, date, or state fact" names the exact condition that selects the alternatives. It also covers the follow-up decision tree — call save_staffing_plan once only if no plan_id is returned, never re-save an existing plan — and tells the agent to omit roles for the catalog path.

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