Skip to main content
Glama

TempGuru Event Staffing

Get Quote Request Status

get_quote_request_status
Read-only

Check whether a TempGuru quote request reference was received by the CRM or durably queued. Use only after the buyer personally submitted a TempGuru website form and received a TG reference, or for a historical reference. The authless MCP prepare_quote_form handoff does not create a reference. This v1 status stub reports received/queued only; it does not yet expose quote_sent or won. get_quote_request_status(reference='TG-ABC234') Status records are retained for 90 days. A not-found result does not prove the CRM lead is absent; follow up with the reference at contactus@tempguru.co.

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": {
      "reference": "<reference>"
    },
    "name": "get_quote_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesTG reference returned after the buyer submits the TempGuru website form, e.g. TG-ABC234.

Output Schema

NameRequiredDescriptionDefault
statusNo
channelNo
messageYes
deal_nameNo
follow_upYes
referenceYes
created_atNo
quote_foundYesDiscriminator. false means the status stub is absent or expired.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world behavior, and the description adds real context beyond them: the v1 stub does not expose quote_sent or won, records are retained 90 days, and a not-found result does not prove the CRM lead is absent. The only gap is that it does not describe latency or queue timing beyond 'durably queued'.

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 the usage constraint are front-loaded and every sentence carries information, including the example and hints. The inline <examples> and <hints> tags make it slightly denser than necessary, but nothing is idle repetition of the schema or annotations.

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 flags the v1 limitation on statuses, the 90-day retention window, and the contactus@tempguru.co fallback. For a single-parameter read tool this is as complete as an agent needs.

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 schema already documents the pattern and example for 'reference'. The description still adds provenance meaning the schema lacks: the reference comes from a personally submitted website form, and the authless prepare_quote_form handoff does not produce one.

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 first sentence states a specific verb and resource: check whether a TempGuru quote request reference was received by the CRM or durably queued. It also scopes the tool as a 'v1 status stub' that reports received/queued only, so an agent knows it is a status lookup and not a quote-detail fetch.

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 precondition (use only after the buyer personally submitted a website form and holds a TG reference, or for a historical reference) and explicitly rules out the sibling path: 'The authless MCP prepare_quote_form handoff does not create a reference.' That is when-to-use plus a named exclusion.

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.