Skip to main content
Glama
TempGuru Event Staffing

TempGuru Event Staffing

Official
by Tempguru-co

Save Staffing Plan

save_staffing_plan

Save a complete event staffing plan for 30 days to share, resume, or link to a later quote request. Use only when planning returns no plan ID and you need to persist the confirmed details.

Instructions

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

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>",
      "roles": "<roles>"
    },
    "name": "save_staffing_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesEvent city, name or slug (e.g. Chicago).
rolesYesConfirmed roles, headcount, hours, and days to recompute and save.
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.

Output Schema

NameRequiredDescriptionDefault
statusYesDiscriminator. Only status:saved means a resumable plan_id exists.
messageYes
plan_idNo12-character reference for the saved non-PII snapshot.
created_atNo
expires_atNoConservative 30-day expiry for the saved snapshot.
plan_statusNoPlanner branch that prevented persistence.
continuationNo
next_actionsYes
resource_uriNoPublic no-store REST URI that restores the saved artifact.
schema_versionNo
quote_readinessNoThe buyer must open the handoff form and personally submit their contact details.
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.3
    • changedOutput schema / properties / created_at / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • changedOutput schema / properties / expires_at / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
  2. Addedv1.7.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, and the description adds substantial context beyond them: the server recomputes rates, totals, lead time, and compliance and rejects caller-supplied pricing. It also explicitly scopes what the tool does NOT do (reserve staff, submit contact details, request a quote) and describes the full status-branch behavior for saved, plan_incomplete, rate_limited, and storage_unavailable.

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 purpose and gating condition are front-loaded before the behavioral warnings, and every sentence carries signal—including the hints block, which is load-bearing for error handling. It is somewhat dense and long, and the 'Provide the same confirmed…' sentence could be tightened, but there is no true filler.

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 documentation is not required, yet the description still explains the status outcomes an agent must branch on. Combined with the explicit non-goals and the input-recomputation rule, an agent has everything needed to invoke this correctly and handle its results.

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?

The description enumerates the inputs to supply ('city, date, event type, attendees, roles, headcount, hours, and days'), which maps to all five top-level parameters plus nested fields. It adds the semantic constraint that these must be the same confirmed values and that no pricing or totals may be supplied—a rule not expressible in the schema. With 100% schema coverage already documenting formats and defaults, this is solid added value rather than full burden-carrying.

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 states a specific verb and resource: 'Explicitly save a complete non-contact staffing plan for 30 days,' with the stated purpose ('shared, resumed, or linked to a later quote request'). It distinguishes itself from plan_staffing and request_quote by name, so an agent can tell which to call 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?

It gives an explicit positive trigger ('only when plan_staffing returned plan_complete:true without a plan_id and the user needs persistence') and an explicit negative trigger ('never call this tool when plan_staffing already returned a plan_id'). The hints block further routes by status code and names the fallback (continuation.form_url) when saving fails.

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