Skip to main content
Glama

TempGuru Event Staffing

Prepare Quote Form

prepare_quote_form
Read-onlyIdempotent

Use only after the buyer reviews a staffing plan and asks to proceed. Requires the saved non-PII plan_id from plan_staffing or save_staffing_plan and returns a prefilled TempGuru-owned review form. This tool never accepts or transmits names, email, phone, company, or other contact details and never creates a CRM lead or quote reference. The buyer must open form_url, review the plan, enter their own details, and submit it; only that submission creates a lead. This is not a reservation and does not guarantee pricing or availability. If a complete plan has continuation.form_url but no plan_id, give that URL directly instead. Never collect contact details for an MCP call; re-run an expired plan.

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": "prepare_quote_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesSaved non-PII plan reference returned by plan_staffing or save_staffing_plan.
skill_idNoOptional canonical TempGuru skill that assembled the plan.
skill_versionNoOptional version of the TempGuru staffing skill used.
source_platformNoOptional agent/platform attribution, e.g. claude-ai, openclaw, or hermes.

Output Schema

NameRequiredDescriptionDefault
messageYesHuman-readable outcome to relay to the buyer.
plan_idYes
form_urlNoPrefilled TempGuru-owned review form. Present only when handoff_ready is true.
next_stepsYesSafe next actions; no agent-side contact collection.
plan_foundYesWhether the supplied non-PII plan_id resolved before expiry.
handoff_readyYestrue when the saved plan resolved and a prefilled buyer form URL was created.
buyer_submission_requiredYesAlways true. The buyer, not the agent, must enter contact details and submit the form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations, it discloses that the tool never accepts or transmits PII, never creates a CRM lead or quote reference, and that the buyer's own form submission is what creates the lead. It also sets expectations that this is not a reservation and does not guarantee pricing or availability, and points to form_url as the required next action. This is exactly the mutation-adjacent context the readOnlyHint/openWorldHint flags 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 when-to-use condition, then negative constraints, then fallback behavior. Every sentence carries actionable information, though the description is dense at five sentences and the final PII instruction slightly restates the earlier 'never accepts' clause.

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 values need not be explained, yet the description still surfaces the one return field that matters operationally: form_url. For a handoff tool with a single required reference, the description covers preconditions, side effects, and next action completely.

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 description coverage is 100%, so all four parameters are already documented, including the plan_id pattern and the skill/attribution fields. The description reinforces that plan_id must come from plan_staffing or save_staffing_plan and hints at expiry, but adds little beyond what the schema already says, so the baseline 3 applies.

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: returns a prefilled TempGuru-owned review form from a saved plan_id. It explicitly distinguishes itself from the plan-building siblings by naming plan_staffing and save_staffing_plan as producers of the required input, so an agent knows this is a downstream handoff step rather than a planning call.

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 a hard precondition (only after the buyer reviews a plan and asks to proceed), an explicit alternative path (if continuation.form_url exists but no plan_id, give that URL directly), and a recovery rule (re-run an expired plan). It also states a firm exclusion: never collect contact details for an MCP call.

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.