Skip to main content
Glama

List countries

list_countries
Read-onlyIdempotent

List the countries that have active EscortFox listings. Returns each country's code (e.g. "DE"), its English name and how many escort and venue listings it has, so you can tell whether the directory covers a place before searching. Use a code as country in list_cities and search_listings.

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_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countriesYesCountries with active listings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "countries": {
      +      "description": "Countries with active listings.",
      +      "items": {
      +        "properties": {
      +          "code": {
      +            "description": "Country code, for `country`.",
      +            "type": "string"
      +          },
      +          "escortCount": {
      +            "description": "Active escort listings.",
      +            "type": "integer"
      +          },
      +          "name": {
      +            "description": "English name.",
      +            "type": "string"
      +          },
      +          "venueCount": {
      +            "description": "Active venue listings.",
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "countries"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered; the description adds useful behavioral context by naming the returned fields (code, English name, listing counts). It doesn't discuss pagination or ordering, but for a small fixed enumeration that is a minor gap.

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 sentences, front-loaded with what it returns, then the reason to call it and the follow-up tools. No filler or redundant restatement of the title.

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?

With an output schema present, the description needn't detail return values, and it still sketches them; with rich annotations and no inputs, nothing an agent needs to call this correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4; the description still adds a small cross-tool hint that the returned code is the value to pass as `country` elsewhere, which is meaningful usage semantics rather than schema restatement.

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?

States a specific verb and resource ('List the countries') plus a meaningful scope qualifier ('that have active EscortFox listings'), which an agent can use to distinguish it from list_cities, list_districts, and other siblings.

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?

Explicitly frames the decision it supports ('tell whether the directory covers a place before searching') and names the downstream tools that consume the returned code (list_cities, search_listings), so the agent knows both when to call it and what to do next.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources