Skip to main content
Glama

TempGuru Event Staffing

by co.tempguru

Get Quote Request Status

get_quote_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 request_quote 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_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 megan@tempguru.co.

Input Schema

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

Output Schema

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

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and description adds limitations: only reports received/queued, not yet quote_sent/won. Also notes 90-day retention and that not-found doesn't mean CRM lead is absent. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise yet comprehensive: first sentence states purpose, then usage constraints, followed by examples and hints in structured sections. No wasted words.

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?

Given the tool has an output schema, the description doesn't need to explain return values. It covers purpose, usage, limitations, and edge cases (not-found fallback), making it complete for this simple tool.

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% with a single parameter, so baseline is 3. Description adds context about when the reference is obtained and includes an example, going beyond the schema description. Minor improvement but not fully compensating for absent shared understanding.

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 clearly states the tool checks if a TempGuru quote request reference was received or queued, with specific context (CRM/queue). It distinguishes from siblings by noting the authless handoff does not create a reference, providing clear scope.

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?

Explicitly states when to use (after buyer submits form and gets TG reference, or for historical reference) and when not to use (authless MCP handoff). Hints provide follow-up for not-found results.

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

All TempGuru Event Staffing toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose with explicit do-not-use cross-references. Pricing tools (get_rate_benchmark vs get_role_pricing) are carefully separated, and plan_staffing vs check_availability serve different granularity needs.

Naming Consistency5/5

All tools use a consistent verb_noun snake_case pattern (get_cities, plan_staffing, request_quote). The verbs are simple and descriptive, with no mixed casing or stylistic inconsistencies.

Tool Count5/5

12 tools is well-scoped for an event staffing domain covering availability, pricing, roles, compliance, planning, persistence, and quote workflows. Each tool earns its place without redundancy.

Completeness4/5

The workflow is well-covered: plan_staffing creates plans, save/get manage persistence, request_quote hands off to a form, and get_quote_status tracks references. Minor gaps exist like lack of plan update/delete and quote status being a stub, but core operations are complete.

Resources