Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

random_cities_detailed_info

Fetch random cities with IATA code, coordinates, timezone, GMT offset, and geoname ID. Provides varied location data for testing or sampling without city-name search.

Instructions

Return a random sample of cities from the reference catalog. Each record has city name, IATA code, country ISO2, latitude, longitude, timezone, GMT offset and geoname id. Records are drawn from a random offset, so repeated calls return different cities. Sampling only: there is no lookup by city name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
number_of_citiesYesNumber of random cities to sample, from 1 to 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedInput schema / properties / number_of_cities / description
      Previous value: -"Number of random cities to return."New value: +"Number of random cities to sample, from 1 to 100."
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / number_of_cities / maximum
      Added value: +100
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / number_of_cities / description
      Added value: +"Number of random cities to return."
    • addedInput schema / properties / number_of_cities / exclusiveMinimum
      Added value: +0
    • changedInput schema / title
      Previous value: -"random_cities_detailed_infoArguments"New value: +"random_cities_detailed_info_toolArguments"
    • changedOutput schema / title
      Previous value: -"random_cities_detailed_infoOutput"New value: +"random_cities_detailed_info_toolOutput"
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully reveals that records come from a random offset and that repeated calls return different cities, but it does not specify edge behavior such as what happens if the requested sample size exceeds the catalog.

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 description is compact and front-loaded, putting the core purpose first and then adding behavior and boundaries. The field-enumeration sentence may partially overlap with the output schema, but it is not padded or verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter sampling tool with a complete schema and an output schema, the description provides enough context: purpose, returned record fields, randomness behavior, and the no-lookup boundary. Nothing critical is missing for correct selection and invocation.

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%, and the schema already documents number_of_cities with type, range, and required status. The tool description adds no further parameter-specific meaning beyond the sampling context, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Return a random sample of cities from the reference catalog.' The field list and the explicit 'no lookup by city name' boundary make it easy to distinguish from lookup and other random-catalog sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly frames the intended use as sampling and explicitly states a when-not condition: 'there is no lookup by city name.' It does not name specific sibling alternatives, so it stops short of full alternative routing.

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