Skip to main content
Glama

List Cities Tool

list_cities
Read-onlyIdempotent

List the cities in a US state that have childcare centers on Kidincare, largest first, with how many centers each has and a link to its city page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "list_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many cities to return.
stateYesUS state name or two-letter code, e.g. "Texas" or "TX".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds genuine behavioral detail beyond that: results are restricted to cities that actually have centers, are ordered largest first, and each entry carries a center count and city-page link. It does not mention what happens when limit truncates results or whether zero-center cities ever appear, which keeps it below a 5.

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?

A single sentence that front-loads the action and scope, then layers sort order and return contents with no redundant or filler wording. Every clause carries information an agent needs.

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

Completeness4/5

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

With no output schema, the description responsibly names the returned fields (center count, city page link) and the ordering. What it omits is the truncation/limit behavior and whether the response is paginated, which matter for a list tool capped at 100.

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% — both 'state' (name or two-letter code) and 'limit' (default 25, max 100) are fully documented in the schema. The description adds only the implicit meaning that state filtering is scoped to cities with centers, which is behavioral rather than parameter-level, so the baseline 3 applies.

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 gives a specific verb ('List') and resource ('cities in a US state'), plus the exact filter ('that have childcare centers on Kidincare'), the sort order ('largest first'), and the per-item payload ('how many centers each has and a link to its city page'). This clearly separates it from get_center and search_centers, which operate on centers rather than city aggregates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'cities ... that have childcare centers' implies the use case (city-level aggregation for a state), but there is no explicit statement of when to prefer this over search_centers or search_guides, and no exclusions or prerequisites. Usage is inferable but not spelled out.

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.

Resources