Skip to main content
Glama

city_gap

Read-onlyIdempotent

Sell-online gap for one city: independent shops in its mapped districts, how many have no website, and how many run Shopify.

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": {
      "city": "<city>"
    },
    "name": "city_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, for example "Nashville"

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 needs no restating. The description does add real behavioral context by disclosing the underlying population (only independent shops inside mapped districts) and the shape of the result (three counts), but it never says what happens for an unrecognized or unmapped city — error, empty result, or partial data.

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?

A single sentence with no filler, front-loading the metric and then enumerating the three components. The condensed 'Sell-online gap' phrasing is slightly opaque on first read, costing a bit of immediate clarity, but nothing is wasted.

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?

For a read-only, single-parameter tool with no output schema, the description adequately characterizes the computed result and its population. The remaining gap is edge-case behavior for cities that are unknown or have no mapped districts, plus no hint about data recency or geographic coverage limits.

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% and there is only one parameter, so the schema already carries the argument definition and an example value. The description's 'for one city' reinforces single-city scoping but adds no format, casing, or disambiguation guidance beyond the schema, which matches the baseline for a fully documented single parameter.

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?

The description names a specific resource and the exact figures returned: independent shops in a city's mapped districts, the count without a website, and the count running Shopify. That is enough for an agent to know what it gets back, but it does not contrast itself with the sibling search_districts, so the boundary between the two is left implicit.

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: 'for one city' suggests a per-city aggregate in contrast to a district-search tool, and 'in its mapped districts' hints that unmapped areas are out of scope. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the routing decision.

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