Skip to main content
Glama

TempGuru Event Staffing

Get Saved Staffing Plan

get_plan
Read-only

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

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 changed
    • 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. Changed1 schema field changed
    • addedOutput schema / properties / offer_note
      Added value: +{
      +  "description": "Published first-order offer note. Snapshot totals remain undiscounted.",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / plan_id / description
      Previous value: -"12-character lookalike-free plan reference returned by plan_staffing."New value: +"12-character lookalike-free plan reference returned by plan_staffing or save_staffing_plan."
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/non-destructive annotations it discloses behavior the annotations cannot: a 30-day expiry, that the plan is non-PII, what a not-found result implies (expired, storage unavailable, or bad ID), and the remediation step (re-run plan_staffing). It also sets an expectation to review the restored plan with the user before quoting.

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?

Effectively four dense sentences with the scope, prohibition, example, and failure handling front-loaded. The <examples> and <hints> wrapper tags add some visual noise that plain sentences would avoid, but no sentence is 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?

For a single-parameter read with a full schema and an output schema, the description covers everything an agent needs: source of the ID, retention cliff, failure interpretation, and the correct next tool. Return-shape detail is correctly omitted since the output schema carries it.

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 is already documented, so this is an above-baseline case. The description adds genuine meaning beyond the schema: the ID must come from the user, plan_staffing, or save_staffing_plan, and must never be guessed or enumerated, plus an inline example of the expected 12-character format.

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 ('Restore a complete non-PII staffing plan') and adds provenance ('created by plan_staffing or save_staffing_plan') plus a 30-day retention window. This distinguishes it cleanly from save_staffing_plan and plan_staffing without needing their schemas.

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 concrete triggering situations (new conversation, platform change, continuing a saved plan before a quote) and an explicit prohibition ('DO NOT guess or enumerate plan IDs'). It also routes forward to prepare_quote_form as the next step, so the agent knows both when to start and what follows.

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.