Skip to main content
Glama

TempGuru Event Staffing

Save Staffing Plan

save_staffing_plan

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 prepare_quote_form 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. Changed1 schema field changed
    • changedOutput schema / properties / next_actions / items / enum
      Previous value: -[
      -  "share",
      -  "revise",
      -  "request_quote",
      -  "plan_again",
      -  "retry_save",
      -  "continue_on_website"
      -]New value: +[
      +  "share",
      +  "revise",
      +  "prepare_quote_form",
      +  "plan_again",
      +  "retry_save",
      +  "continue_on_website"
      +]
  2. Changed2 schema fields changed
    • 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))$"
  3. Changed3 schema fields changed
    • changedInput schema / properties / event_date / description
      Previous value: -"Event date, ISO YYYY-MM-DD preferred."New value: +"Event date as YYYY-MM-DD; legacy recognizable dates are still accepted."
    • addedInput schema / properties / event_date / format
      Added value: +"date"
    • addedInput schema / properties / event_type / enum
      Added value: +[
      +  "trade-show",
      +  "conference",
      +  "festival",
      +  "concert",
      +  "sporting-event",
      +  "corporate",
      +  "brand-activation",
      +  "other"
      +]
  4. Changed3 schema fields changed
    • changedOutput schema / properties / next_actions / items / enum
      Previous value: -[
      -  "share",
      -  "revise",
      -  "request_quote",
      -  "plan_again",
      -  "retry_save",
      -  "continue_on_website",
      -  "request_quote_without_plan_id"
      -]New value: +[
      +  "share",
      +  "revise",
      +  "request_quote",
      +  "plan_again",
      +  "retry_save",
      +  "continue_on_website"
      +]
    • changedOutput schema / properties / quote_readiness / const
      Previous value: -"needs_contact"New value: +"buyer_submission_required"
    • changedOutput schema / properties / quote_readiness / description
      Previous value: -"The plan is complete; contact details are still required before request_quote."New value: +"The buyer must open the handoff form and personally submit their contact details."
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Well beyond the annotations, it discloses that the server recomputes rates, totals, lead time and compliance and rejects caller-supplied pricing, plus that it does not reserve staff, submit contact details, or request a quote. The hints enumerate the outcome branches (saved, plan_incomplete, rate_limited, storage_unavailable) and what each requires. It does not discuss re-invocation behavior, which matters given idempotentHint=false.

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, preconditions, input contract, and exclusions are front-loaded in that order, and every sentence carries a rule or constraint. The hints block is dense but earns its place; slight redundancy between 'explicitly save' and the surrounding persistence wording.

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?

For a mutation tool with an output schema, this is complete: preconditions, input contract, side effects, exclusions, and error-branch handling are all covered, and return-value detail is correctly delegated to the output schema.

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 the baseline would be 3, but the description adds real meaning: the caller must pass the same confirmed city, date, event type, attendees, roles, headcount, hours and days, and pricing/totals are explicitly not accepted as input. That constraint is not expressible from the schema alone.

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 ('save a complete non-contact staffing plan for 30 days') plus the downstream reasons to save (share, resume, link to quote request). It explicitly separates itself from plan_staffing by operating only on an already-complete plan.

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 an explicit positive condition (plan_staffing returned plan_complete:true without a plan_id and the user needs persistence) and an explicit prohibition (never when a plan_id already exists). It also names the alternative path when persistence fails, pointing to continuation.form_url because prepare_quote_form requires a saved plan_id.

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.