Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

random_countries_detailed_info

Get a random sample of 1-100 countries with capitals, continents, ISO codes, currency, phone prefix, and population. Each call returns a different set.

Instructions

Return a random sample of countries from the reference catalog. Each record has country name, capital, continent, ISO2, ISO3 and numeric ISO codes, FIPS code, currency name and code, phone prefix and population. Records are drawn from a random offset, so repeated calls return different countries. Sampling only: there is no lookup by country name or code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
number_of_countriesYesNumber of random countries 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_countries / description
      Previous value: -"Number of random countries to return."New value: +"Number of random countries to sample, from 1 to 100."
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / number_of_countries / maximum
      Added value: +100
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / number_of_countries / description
      Added value: +"Number of random countries to return."
    • addedInput schema / properties / number_of_countries / exclusiveMinimum
      Added value: +0
    • changedInput schema / title
      Previous value: -"random_countries_detailed_infoArguments"New value: +"random_countries_detailed_info_toolArguments"
    • changedOutput schema / title
      Previous value: -"random_countries_detailed_infoOutput"New value: +"random_countries_detailed_info_toolOutput"
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the random-offset mechanism, that repeated calls return different countries, and that the tool only samples rather than supports lookups. This gives an agent an accurate model of the tool's runtime behavior.

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?

The description is four sentences, each earning its place: purpose, output fields, randomness behavior, and the sampling-only limitation. It is front-loaded with the core action and avoids unnecessary elaboration or repetition.

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 single-parameter sampling tool with an output schema, the description adequately explains what records contain, how randomness works, and the tool's boundary. Nothing critical for selecting or invoking the tool is missing; an agent can confidently call it based on this definition.

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?

The input schema already provides 100% description coverage for the single parameter, including its range and meaning. The tool description does not add any extra parameter-specific semantics beyond what the schema states, so a baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Return a random sample of countries from the reference catalog.' It clearly distinguishes this tool from siblings that target cities, airports, aircraft, or flights, and the explicit 'Sampling only' statement reinforces that it is not a lookup tool.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool (when a random country sample is needed) and when not to use it: 'there is no lookup by country name or code.' This exclusion is clear enough to prevent an agent from calling it for deterministic retrieval, even without naming an alternative sibling.

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