Skip to main content
Glama
Sign In
snapp-mcp

snapp-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List cities

list_cities
Read-onlyIdempotent

Retrieve the cities served, including IDs, names and center coordinates, to identify valid delivery areas. Filter by Persian title or English code such as 'شیراز'.

Instructions

List cities Snappfood serves, with id, names and center coordinates.

Centers work as a rough delivery point.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
queryNoPersian title or English code, e.g. 'شیراز'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • removedInput schema / properties / query / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / query / description
      Previous value: -"Filter on Persian title or English code, e.g. 'شیراز'."New value: +"Persian title or English code, e.g. 'شیراز'."
    • addedInput schema / properties / query / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed4 schema fields changedv0.2.0
    • changedInput schema / properties / query / description
      Previous value: -"Optional filter on the Persian title or English code, e.g. 'شیراز' or 'Shiraz'."New value: +"Filter on Persian title or English code, e.g. 'شیراز'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"list_citiesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "list_citiesDictOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this as a safe, read-only, idempotent, open-world operation. The description adds useful behavioral context by naming the returned fields and warning that center coordinates are only a rough delivery point.

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?

Two short sentences, front-loaded with the core action and return fields, followed by a useful caveat. No unnecessary wording or repetition.

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 simple read-only city-listing tool with one fully described optional parameter and no output schema, the description covers purpose, returned fields, and a relevant caveat. It could do slightly more by routing users away from related location siblings, but it is broadly complete.

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%, so the single query parameter is already fully documented in the schema. The description does not add meaning about how the query filters or matches Persian titles versus English codes.

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 states a specific verb and resource: list cities served by Snappfood, including id, names, and center coordinates. It is clear what the tool does, but it does not explicitly distinguish itself from location-related siblings such as find_location or reverse_geocode.

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 implied: the tool is for looking up cities Snappfood serves, optionally narrowed by the query parameter. However, there is no explicit guidance on when to use this versus find_location or reverse_geocode, and no exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools