Skip to main content
Glama
TempGuru Event Staffing

TempGuru Event Staffing

Official
by Tempguru-co

Get Cities

get_cities
Read-only

Lists configured market entries by tier, state, or country and matches one city against the catalog. Check if a market is listed; catalog presence does not confirm availability or coverage.

Instructions

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. Configured entries are planning data; the public coverage claim is 300+ U.S. and Canadian markets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cities"
  }
}

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.7.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "Optional single-city catalog match (nickname/borough aware). Returns catalog_match plus a suggestion; never a coverage promise.",
      +  "type": "string"
      +}
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Optional country filter: 'US' or 'CA'.",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Optional cap on the number of cities returned (full counts still in total/tier_breakdown).",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "catalog_check": {
      +      "const": true,
      +      "description": "Present when a single-city catalog check was requested.",
      +      "type": "boolean"
      +    },
      +    "catalog_match": {
      +      "description": "Whether the city resolved to a configured catalog entry; not an availability or coverage promise.",
      +      "type": "boolean"
      +    },
      +    "catalog_qualification": {
      +      "type": "string"
      +    },
      +    "cities": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "country": {
      +            "description": "US or CA.",
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "state": {
      +            "type": "string"
      +          },
      +          "state_abbr": {
      +            "type": "string"
      +          },
      +          "tier": {
      +            "description": "Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets.",
      +            "enum": [
      +              "hub",
      +              "mid",
      +              "small"
      +            ],
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "City detail page on tempguru.co.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name",
      +          "state",
      +          "state_abbr",
      +          "country",
      +          "tier",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "city": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "country": {
      +              "description": "US or CA.",
      +              "type": "string"
      +            },
      +            "name": {
      +              "type": "string"
      +            },
      +            "slug": {
      +              "type": "string"
      +            },
      +            "state": {
      +              "type": "string"
      +            },
      +            "state_abbr": {
      +              "type": "string"
      +            },
      +            "tier": {
      +              "description": "Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets.",
      +              "enum": [
      +                "hub",
      +                "mid",
      +                "small"
      +              ],
      +              "type": "string"
      +            },
      +            "url": {
      +              "description": "City detail page on tempguru.co.",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "slug",
      +            "name",
      +            "state",
      +            "state_abbr",
      +            "country",
      +            "tier",
      +            "url"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The matched configured entry, or null when there was no catalog match."
      +    },
      +    "coverage_confirmation_required": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "description": "Present when the list was truncated by limit.",
      +      "type": "string"
      +    },
      +    "requested": {
      +      "type": "string"
      +    },
      +    "returned": {
      +      "description": "Number of cities in the cities array (after limit).",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "suggestion": {
      +      "additionalProperties": false,
      +      "description": "Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply.",
      +      "properties": {
      +        "kind": {
      +          "enum": [
      +            "city",
      +            "role"
      +          ],
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "slug": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "slug",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "tier_breakdown": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "hub": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "mid": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        },
      +        "small": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "hub",
      +        "mid",
      +        "small"
      +      ],
      +      "type": "object"
      +    },
      +    "total": {
      +      "description": "Total cities matching the filter (before limit).",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv1.0.0

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, openWorldHint=false, and destructiveHint=false. The description adds meaningful behavioral context: configured entries are planning data, catalog presence does not promise availability or coverage, a coordinator must confirm orders, unfiltered results are capped, and the public coverage claim is 300+ markets. This goes well beyond the structured annotations.

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 description is dense but front-loaded with the core purpose and caveat, followed by use cases, examples, and hints. It is longer than the minimum, but every section earns its place given the semantic pitfalls an agent must avoid. The structure is organized and scannable.

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 lookup tool with 100% parameter documentation and an output schema, the description supplies all needed context: when to use it, how to answer common user questions, what caveats to preserve, how filters behave, and what sibling tools cover adjacent needs. Nothing material is missing for correct invocation.

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?

Schema coverage is 100%, but the description still adds value by clarifying accepted formats ('CA' or 'California' for state, 'US' or 'CA' for country), nickname/borough resolution, the meaning of limit caps with full counts retained, and the fact that city matching returns a suggestion rather than a coverage promise. These nuances are not fully captured in the schema.

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 a specific verb and resource: 'List configured market entries by tier, or match one city.' It clearly distinguishes this tool from siblings like check_availability and get_role_pricing, and explicitly names the non-goal: catalog presence is not availability or order coverage.

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 gives concrete query patterns ('What markets are configured in [state]?', 'Is [city] in the catalog?'), provides example calls for several filter combinations, and explicitly names sibling tools for related tasks (get_role_pricing, check_availability, plan_staffing). It even instructs how to handle 'Do you cover [city]?' with the proper caveat.

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