Skip to main content
Glama
pdichone

SQLite Geography Server

by pdichone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_cities_in_country

Retrieve cities in a specific country by providing its two-letter country code. Use the limit parameter to cap the number of results.

Instructions

Get cities in a specific country.

Args:
    country_code: Two-letter country code (e.g., "US", "GB", "FR")
    limit: Maximum number of cities to return (default 50)

Returns:
    List of cities in the country

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
country_codeYes

Output Schema

TableJSON 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 behavioral burden. It discloses the default limit of 50 and that a list of cities is returned, but says nothing about pagination, behavior on invalid/unknown country codes, or how the limit interacts with total results.

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?

The purpose sentence is front-loaded and the Args/Returns structure is easy to scan. The labeling is slightly boilerplate-heavy for a two-parameter tool, but no sentence 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?

An output schema exists, so return-value detail is not required, and both parameters are documented with format and defaults. What remains thin is error handling and pagination semantics, which are minor for a simple read tool.

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%, so the description must compensate, and it does: country_code is defined as a two-letter code with concrete examples ('US', 'GB', 'FR'), and limit is explained as a maximum count with a stated default of 50.

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 and resource with scope: retrieving cities within one country. It does not, however, distinguish itself from the sibling search_cities (keyword lookup) or get_states_in_country, leaving the agent to infer the boundary.

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 by the phrase 'in a specific country', which suggests a country-scoped enumeration versus keyword search, but no explicit when-to-use or when-not-to-use statement is given, and no alternative is named.

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