Retrieve the list of cities where SnappFood delivery service is available. Use it to check if a location is covered before ordering or to display supported areas.
List covered cities
| Name | Required | Description | Default |
|---|---|---|---|
| token | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'List' weakly implies a read-only, non-destructive operation, but nothing is said about authentication requirements, rate limits, pagination, or whether results are cached or region-scoped.
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?
Three words are technically brief and front-loaded, but this is under-specification rather than conciseness. The single sentence leaves every substantive question about the tool unanswered.
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?
For a tool with an undocumented parameter, no annotations, and no output schema, the description supplies almost nothing. It should at minimum explain what 'covered cities' means and what the token parameter does.
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?
There is one parameter (token) at 0% schema description coverage, and the description never mentions it or any other input. With the schema silent and the description silent, the caller has no idea what the parameter is for.
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 verb ('List') and a resource ('covered cities'), so the basic operation is inferable. However, 'covered' is undefined, and the description does nothing to separate this from siblings like geo, food_area, or food_place, so an agent cannot tell whether this lists service-coverage zones or geographic city data.
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?
There is no when-to-use, when-not-to-use, or alternative-tool guidance at all. The reader must infer from the name alone that this is the entry point for city coverage, and nothing indicates whether it should be called before food_area or instead of geo.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.