Skip to main content
Glama

search_districts

Read-onlyIdempotent

Find shopping districts among 721 in US and Canadian cities by city or name. Returns shops, website share and Shopify share.

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": {
      "query": "<query>"
    },
    "name": "search_districts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 20, max 50
queryYesCity or district name, for example "Toronto" or "Lincoln Road"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the dataset size and the returned metrics, which helps an agent judge result expectations, but says nothing about match behavior for ambiguous city names or result ordering.

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?

Two short sentences, front-loaded with the action and scope, with no redundant phrasing. The dataset-size figure earns its place by setting expectations about coverage, though it borders on trivia.

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 usefully lists the returned fields, and the two-parameter schema is fully self-documenting. For a simple read-only search tool this is nearly complete; only ambiguous-match behavior is left unstated.

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 description coverage is 100%, with both query and limit documented including default and max, so the baseline is 3. The phrase "by city or name" echoes the query parameter without adding matching rules or format guidance beyond the schema's own examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Find shopping districts") plus concrete scope (721 districts across US and Canadian cities) and search keys (city or name). It also names what comes back (shops, website share, Shopify share). It does not distinguish itself from the sibling city_gap, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is the lookup to call when it has a city or district name. There is no statement of when to prefer it over city_gap, no exclusions, and no note on what to do when the query matches nothing.

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