Skip to main content
Glama
Tempguru-co

TempGuru Event Staffing

Official

Request Quote

request_quote

Submit event staffing details to receive a human-reviewed quote within one business day. Creates a structured lead for coordinator follow-up.

Instructions

Submit a staffing request to TempGuru. Use this after confirming city coverage, role pricing, and availability with the other tools. Creates a structured lead in TempGuru's CRM — a human coordinator will review and respond with a quote within one business day. Not a reservation; does not guarantee pricing or availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_nameYesFull name of the contact person
contact_emailYesContact email address for the quote response
companyYesCompany or organization name
event_nameYesName of the event (e.g. 'HIMSS 2026', 'Brand Fest Austin')
event_typeYesEvent type: trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other
cityYesCity where the event is held
event_datesYesEvent dates as a human-readable string, e.g. 'June 15–17, 2026'
rolesYesRoles and headcount needed for the event
budget_rangeNoEstimated total budget range if calculated, e.g. '$8,400–$12,600'
attireNoStaff attire requirements
special_requirementsNoAny special requirements: language skills, certifications, overnight shifts, etc.
compliance_notesNoAny compliance flags surfaced by get_compliance_by_state
Behavior5/5

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

Discloses asynchronous behavior (human coordinator reviews within one business day) and limitations (not a reservation, no guarantee). Annotations are minimal, so description compensates well.

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 at three sentences, front-loaded with action, followed by usage context and disclaimers. No superfluous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description explains the process and when to use, it omits what the tool immediately returns (e.g., a lead ID). With no output schema, this leaves a gap in completeness.

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 coverage is 100%, so description need not add much. It does not elaborate on parameter meanings beyond schema, earning a baseline 3.

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 submits a staffing request to TempGuru, creating a structured lead. It distinguishes itself from sibling tools by noting it should be used after checking coverage, pricing, and availability with other tools.

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 guides when to use (after confirming with other tools) and what not to expect (not a reservation, no guarantee). This helps the agent avoid misuse.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tempguru-co/tempguru-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server