Skip to main content
Glama

TempGuru Event Staffing

by co.tempguru

Get Cities

get_cities
Read-only

List configured market entries by tier, or match one city. Catalog presence is not availability or order coverage; check_availability gives tier-based lead-time guidance only, and a coordinator confirms each order after buyer submission. Use for 'What markets are configured in [state]?', 'Is [city] in the catalog?', or 'Which Canadian markets are listed?'. For 'Do you cover [city]?' pass city='[name]', report the catalog match or suggestion, and preserve the coordinator-confirmation caveat. Use get_role_pricing for rates, check_availability for dates, or plan_staffing for a full plan. get_cities(city='Brooklyn') ; get_cities(state='TX') ; get_cities(tier='hub', country='CA') ; get_cities(limit=25) State accepts 'CA' or 'California'; country accepts US or CA. City resolves nicknames and boroughs. Unfiltered results are capped; use filters or limit. 345 configured entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional single-city catalog match (nickname/borough aware). Returns catalog_match plus a suggestion; never a coverage promise.
tierNoOptional filter to one tier only.
limitNoOptional cap on the number of cities returned (full counts still in total/tier_breakdown).
stateNoOptional 2-letter state code (e.g., 'CA') or full state name.
countryNoOptional country filter: 'US' or 'CA'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoThe matched configured entry, or null when there was no catalog match.
noteNoPresent when the list was truncated by limit.
totalNoTotal cities matching the filter (before limit).
citiesNo
messageNo
returnedNoNumber of cities in the cities array (after limit).
requestedNo
suggestionNoClosest known city/role for a miss. Confirm with the user before using it; do not auto-apply.
catalog_checkNoPresent when a single-city catalog check was requested.
catalog_matchNoWhether the city resolved to a configured catalog entry; not an availability or coverage promise.
tier_breakdownNo
catalog_qualificationNo
coverage_confirmation_requiredNo

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes much further: it reveals that catalog presence is not availability, that a coordinator confirms orders, that unfiltered results are capped, and that city resolution handles nicknames/boroughs. These are non-obvious behaviors an agent must know to set expectations.

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?

The description is dense but efficiently structured: a clear lead sentence, usage guidance, caveats, examples, and hints. Every sentence adds actionable information, and the use of <examples> and <hints> sections makes it scannable. No filler or redundancy.

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 read-only catalog tool, the description covers all critical context: purpose, when to use (and when not to), parameter behaviors, output interpretation (catalog match vs. suggestion, totals/tier_breakdown), and limitations (cap, coordinator confirmation). With annotations and an output schema present, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though input schema coverage is 100%, the description enriches parameters significantly: it explains that state accepts both codes and full names, city resolves nicknames/boroughs, limit caps results but still returns full counts in total/tier_breakdown, and provides valid usage examples like get_cities(tier='hub', country='CA'). This is valuable beyond the schema's field descriptions.

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 opens with 'List configured market entries by tier, or match one city,' which is a clear, specific verb+resource statement that immediately distinguishes the tool from siblings like check_availability and get_role_pricing. It also includes concrete example queries and clarifies the catalog-only 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?

The description explicitly tells the agent when to use this tool ('Use for...'), when not to use it (not for availability/coverage), and names alternatives: 'Use get_role_pricing for rates, check_availability for dates, or plan_staffing for a full plan.' This is model guidance beyond what siblings provide.

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