List the cities gigstamp currently covers, with their listing URLs and, on a big city, the named districts search_gigs_and_events can narrow to. Call this first: only these cities return data.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the burden; it discloses the coverage constraint ('only these cities return data') and the shape of the returned data, including that districts are only present for big cities. It doesn't discuss caching or whether the list is exhaustive/stale, a minor gap for a zero-param read.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler, and the critical 'Call this first' directive is front-loaded after the purpose statement. Every clause (coverage, URLs, big-city districts) earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description must convey return values, and it does (cities, listing URLs, districts for big cities). Combined with the usage directive, an agent has everything needed to call a zero-param tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so the baseline of 4 applies; nothing in the description can or needs to add parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List the cities gigstamp currently covers') plus the payload shape (listing URLs, named districts). It also names the sibling search_gigs_and_events, so an agent can distinguish it from the other listing tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Call this first: only these cities return data' gives an explicit ordering rule and the reason for it, which is rare and useful. It stops short of stating when-not-to-use or full alternatives, so a 4 rather than a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
