Skip to main content
Glama

TempGuru Event Staffing

Get Cities

get_cities
Read-only

List configured market entries by tier, or match one city. Catalog presence is not availability or order coverage; get_lead_time_guidance 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, get_lead_time_guidance for dates, or plan_staffing for a 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. Changed8 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Optional single-city coverage check (nickname/borough aware). Returns covered yes/no + suggestion."New value: +"Optional single-city catalog match (nickname/borough aware). Returns catalog_match plus a suggestion; never a coverage promise."
    • addedOutput schema / properties / catalog_check
      Added value: +{
      +  "const": true,
      +  "description": "Present when a single-city catalog check was requested.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / catalog_match
      Added value: +{
      +  "description": "Whether the city resolved to a configured catalog entry; not an availability or coverage promise.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / catalog_qualification
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / city / description
      Previous value: -"The matched market (coverage check), or null if not covered."New value: +"The matched configured entry, or null when there was no catalog match."
    • removedOutput schema / properties / coverage_check
      Removed value: -{
      -  "const": true,
      -  "description": "Present when a single-city coverage check was requested.",
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / coverage_confirmation_required
      Added value: +{
      +  "const": true,
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / covered
      Removed value: -{
      -  "type": "boolean"
      -}
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changed
    • changedOutput schema / properties / cities / items / properties / tier / description
      Previous value: -"Market tier: hub = 25 major metros, mid = 129 secondary markets, small = 191 tertiary markets."New value: +"Market tier: hub = 25 major metros, mid = 128 secondary markets, small = 192 tertiary markets."
    • changedOutput schema / properties / city / anyOf
      Previous value: -[
      -  {
      -    "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 = 129 secondary markets, small = 191 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"
      -  }
      -]New value: +[
      +  {
      +    "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"
      +  }
      +]
  4. Changed1 schema field changed
    • changedOutput schema / properties / suggestion / description
      Previous value: -"Closest known city/role for a miss; retry with this slug."New value: +"Closest known city/role for a miss. Confirm with the user before using it; do not auto-apply."
  5. Changed13 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "Optional single-city coverage check (nickname/borough aware). Returns covered yes/no + suggestion.",
      +  "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"
      +}
    • addedOutput schema / properties / city
      Added value: +{
      +  "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 = 129 secondary markets, small = 191 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 market (coverage check), or null if not covered."
      +}
    • addedOutput schema / properties / coverage_check
      Added value: +{
      +  "const": true,
      +  "description": "Present when a single-city coverage check was requested.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / covered
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / message
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "Present when the list was truncated by limit.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / requested
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / returned
      Added value: +{
      +  "description": "Number of cities in the cities array (after limit).",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / suggestion
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Closest known city/role for a miss; retry with this slug.",
      +  "properties": {
      +    "kind": {
      +      "enum": [
      +        "city",
      +        "role"
      +      ],
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "slug": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "slug",
      +    "name"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / total / description
      Previous value: -"Number of cities matching the filter."New value: +"Total cities matching the filter (before limit)."
    • removedOutput schema / required
      Removed value: -[
      -  "total",
      -  "tier_breakdown",
      -  "cities"
      -]
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "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 = 129 secondary markets, small = 191 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"
      +    },
      +    "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": "Number of cities matching the filter.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "tier_breakdown",
      +    "cities"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, and the description adds real context on top: catalog presence is not availability or order coverage, a coordinator confirms each order after buyer submission, and unfiltered results are capped. The only minor gap is it doesn't quantify the default cap, only that one exists and that total/tier_breakdown counts remain full.

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

Conciseness3/5

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

The core statement and routing are front-loaded and the example/hint blocks are scannable, but there is duplication: get_lead_time_guidance is mentioned twice and the coordinator-confirmation caveat appears twice. A modest trim would keep the same information with less noise.

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 five-parameter, fully documented, zero-required read tool with an output schema, the description covers filtering modes, the cap behavior, the semantic caveat distinguishing catalog from coverage, and every relevant sibling alternative. Nothing an agent needs to call it or interpret a match correctly is missing.

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 baseline is 3, but the hints add accepted forms beyond the schema: state takes 'CA' or 'California', country takes US or CA, and city resolves nicknames and boroughs. It also clarifies that limit caps rows while full counts persist, which sharpens the schema's wording rather than merely repeating it.

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?

Opens with a specific verb and resource: 'List configured market entries by tier, or match one city,' which covers both the list and single-city modes. It explicitly separates itself from get_lead_time_guidance, get_role_pricing, and plan_staffing, so an agent can route without inspecting schemas.

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?

Gives concrete triggering questions ('What markets are configured in [state]?', 'Is [city] in the catalog?') plus explicit exclusions routed to named alternatives for rates, dates, and staffing plans. It even prescribes how to answer a coverage question: pass city, report the match or suggestion, and preserve the coordinator caveat.

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.