Skip to main content
Glama

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

TableJSON Schema
NameRequiredDescriptionDefault
qNo
pageNo
sortNo
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
limitNo
contextNoOptional: 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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, so the safety profile is covered. The description adds a valuable behavioral caveat: 'Membership is derived and known to be partial: read a count as a floor, not a census.' This is beyond annotations and informs how to interpret results. No contradiction. Could mention pagination but not necessary for a browse tool.

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?

Two sentences with no fluff. The first sentence establishes purpose and sibling context; the second gives usage and the critical caveat. Well front-loaded, efficient, and every clause earns its place. Slightly dense but appropriate.

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?

For a simple browse/search tool with 6 parameters and no output schema, the description covers purpose, usage context, sibling differentiation, and the partial-data caveat. It does not describe the return format or pagination behavior, but these are less critical for a read-only search tool. The annotation covers read-only nature. Overall complete enough for an agent to invoke correctly.

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 low (33%), with only `type` and `context` described. The description compensates partially by explaining 'Search by text' (maps to `q`) and 'sort by provider count' (maps to `sort`). It does not clarify `page` or `limit`, but these are standard and self-explanatory. Given the low coverage, the description adds some meaning but not complete coverage.

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 ('Browse'), resource ('the country dimension'), and a clear use case ('who is in Germany'). Explicitly distinguishes from siblings by naming find_industries / find_regions / find_areas and positioning this as the finest taxonomy and the one a buyer names. Purpose is unambiguous and differentiates from sibling tools without opening schemas.

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?

Gives clear context for when to use ('the one a buyer usually names') and names the peer tools as alternatives. Does not explicitly state when NOT to use or provide exclusion conditions, but the context is strong enough for an agent to infer the right choice. No misleading guidance.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources