Skip to main content
Glama
TempGuru Event Staffing

TempGuru Event Staffing

Official
by Tempguru-co

Get Saved Staffing Plan

get_plan
Read-only

Restore a saved non-PII staffing plan using its 12-character ID so buyers can continue a previous plan across conversations or platforms before requesting a quote.

Instructions

Restore a complete non-PII staffing plan created by plan_staffing or save_staffing_plan within the last 30 days. Use when a buyer starts a new conversation, changes agent platforms, or wants to continue a saved plan before requesting a quote. DO NOT guess or enumerate plan IDs; use only the 12-character plan_id the user, plan_staffing, or save_staffing_plan supplied. get_plan(plan_id='ABCDEFGH2345') A not-found result means the plan expired, storage was unavailable, or the ID is wrong; re-run plan_staffing. Review the restored plan with the user before request_quote.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes12-character lookalike-free plan reference returned by plan_staffing or save_staffing_plan.

Output Schema

NameRequiredDescriptionDefault
messageYes
plan_idYes
snapshotNo
next_stepsYes
plan_foundYesDiscriminator. false means the reference was absent or expired.
continuationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.7.3
    • removedOutput schema / properties / offer_note
      Removed value: -{
      -  "description": "Published first-order offer note. Snapshot totals remain undiscounted.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / snapshot / properties / compliance_jurisdiction / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / snapshot / properties / compliance_jurisdiction / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / snapshot / properties / event / properties / event_date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / snapshot / properties / event / properties / event_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / snapshot / properties / event / properties / event_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / snapshot / properties / event / properties / event_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / snapshot / properties / source / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / snapshot / properties / source / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  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 readOnly/non-destructive, and the description adds information annotations cannot express: a 30-day retention window, non-PII status, anti-enumeration constraints, and the three distinct causes of a not-found result. That is exactly the behavioral context an agent needs to interpret failures rather than retry blindly.

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 usage conditions are front-loaded and there is no filler prose. The trailing hints section re-states the 30-day expiry already mentioned in the first sentence, and the XML-style tags add mild visual bulk, but each block is scannable and earns its place.

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?

With an output schema present, return values need not be described, and the description covers everything else: provenance of the ID, retention limit, failure interpretation, and the required user-review step before request_quote. Nothing an agent needs to call it correctly 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 coverage is 100% and the pattern already encodes the 12-character lookalike-free format, so the schema carries most of the weight. The description still adds sourcing semantics ('use only the ... plan_id the user, plan_staffing, or save_staffing_plan supplied') and a concrete example call, going beyond a bare restatement.

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 uses a specific verb ('Restore') plus a clearly scoped resource ('complete non-PII staffing plan') and names both producers (plan_staffing, save_staffing_plan), which cleanly separates it from the mutating siblings with similar names. An agent can tell immediately that this is the read-back counterpart to save_staffing_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?

Explicit triggers are given ('buyer starts a new conversation, changes agent platforms, or wants to continue a saved plan before requesting a quote') along with a hard prohibition ('DO NOT guess or enumerate plan IDs') and a recovery path on failure ('re-run plan_staffing'). It also sequences the tool relative to request_quote, which is genuine when/when-not guidance.

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