Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

find_countries

Read-only

Browse the country dimension — the finest of the four place taxonomies, and the one a buyer usually names ("who is in Germany"). Peer to find_industries / find_regions / find_areas. Search by text; sort by provider count. Membership is derived and known to be partial: read a count as a floor, not a census.

Input Schema

NameRequiredDescriptionDefault
qNoFree text matched against name and description, e.g. "payments".
pageNoPage number, 1-based (default 1).
sortNoOrder, e.g. "name" or "provider_count".
typeNoWhich record kind to list. `country` (default) is the dimension itself — the 27 countries the catalog covers; `country-industry` is the crossover pages ("Education & EdTech in China"); `all` is both.country
limitNoResults per page, 1-100 (default 25).
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / q / description
      Added value: +"Free text matched against name and description, e.g. \"payments\"."
    • addedInput schema / properties / sort / description
      Added value: +"Order, e.g. \"name\" or \"provider_count\"."
  3. Changed1 schema field changed
    • addedInput schema / properties / type
      Added value: +{
+  "default": "country",
+  "description": "Which record kind to list. `country` (default) is the dimension itself — the 27 countries the catalog covers; `country-industry` is the crossover pages (\"Education & EdTech in China\"); `all` is both.",
+  "enum": [
+    "country",
+    "country-industry",
+    "all"
+  ],
+  "type": "string"
+}
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: "Membership is derived and known to be partial: read a count as a floor, not a census," which warns the agent about data reliability in a way no structured field conveys.

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?

Front-loaded with the resource identity, then taxonomy relationship, then mechanics, then the data-quality caveat. Dense and largely waste-free, though the taxonomy aside is slightly expansive.

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 no output schema, the definition still gives the agent enough: what the dimension contains, the record-kind modes, and the critical caveat that counts are floors. Return-format gaps are minor since the tool is a simple filtered list.

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 coverage is 100%, so the schema already documents all six parameters. The description restates the search-by-text and sort-by-count behavior already present in the schema, adding no syntax or format details beyond it. Baseline 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?

States a specific verb and resource ("Browse the country dimension") and situates it precisely within the place taxonomy, explicitly naming its peers find_industries / find_regions / find_areas. An agent can tell it apart from siblings without opening any schema.

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 clarifies that this is the finest of four place taxonomies and "the one a buyer usually names," which is genuine routing guidance, and names the peer tools. It stops short of explicit when-not-to-use conditions, e.g. when to call get_country or find_regions instead.

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

All apis-io toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources