Skip to main content
Glama
Sign In
SQLite Geography Server

SQLite Geography Server

by pdichone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_cities

Find cities by name, with optional two-letter country code filtering, to retrieve matching locations from geographic data.

Instructions

Search for cities by name and optionally filter by country.

Args:
    name: City name to search for (partial matches allowed)
    country_code: Two-letter country code to filter by (optional)

Returns:
    List of cities matching the search criteria

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": "search_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
country_codeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that matching is partial and the return is a list, but says nothing about result limits, pagination, performance, or what happens when name is left at its empty default – an important behavioral question for a search endpoint.

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?

Short and front-loaded, with the core purpose in the first sentence and Args/Returns following. The Args block slightly duplicates the sentence above but stays within useful bounds.

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 an output schema present, the Returns line need only be minimal, and both parameters are explained. The remaining gap is behavior at default/empty inputs, which neither annotations nor description cover.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% (only titles/defaults), so the description does the work: it clarifies that name allows partial matches and that country_code is a two-letter code, which is exactly the semantics the schema lacks. It doesn't address the empty-string defaults.

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+resource ("Search for cities") plus the filtering dimension (country). It is distinguishable from list-style siblings such as get_cities_in_country, though it never names those siblings explicitly.

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?

Implies usage: search when you have a name fragment, filter by country optionally. But with siblings like get_cities_in_country and search_countries in the same family, the description offers no explicit rule for choosing among them and no exclusions.

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