Skip to main content
Glama

Countries

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Countries By Region

countries_by_region
Read-onlyIdempotent

List all countries in a region (e.g., "Africa", "Europe", "Asia"). Returns name, capital, population, area, and flag emoji.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesRegion name — one of: africa, americas, asia, europe, oceania

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of countries in region
regionYesRegion name queried
countriesYesCountries in the region sorted by population descending

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / countries / items / properties / population / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of countries in region",
+      "type": "integer"
+    },
+    "countries": {
+      "description": "Countries in the region sorted by population descending",
+      "items": {
+        "properties": {
+          "capital": {
+            "description": "Capital city or N/A if not available",
+            "type": "string"
+          },
+          "flag": {
+            "description": "Flag emoji or empty string",
+            "type": "string"
+          },
+          "name": {
+            "description": "Common country name",
+            "type": "string"
+          },
+          "population": {
+            "description": "Total population",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "name",
+          "capital",
+          "population",
+          "flag"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "region": {
+      "description": "Region name queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "region",
+    "count",
+    "countries"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "region": "europe"
+  },
+  {
+    "region": "asia"
+  }
+]
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds only the enumeration of returned fields, which largely duplicates the output schema rather than disclosing behavior like ordering or result caps.

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?

One tight sentence plus a return-field clause; purpose is front-loaded and nothing is wasted.

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 a full input schema, an output schema, and rich annotations, the definition covers everything needed to call the tool. The one real gap is sibling disambiguation, which belongs in usage guidance rather than in a return-value description.

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 enumerates the five valid region values, so the description's region examples add little beyond the structured field. Baseline 3 applies since the schema does the heavy lifting.

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

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List all countries in a region') and gives concrete region examples, so an agent immediately knows what it returns. It does not distinguish itself from near-siblings like countries_by_currency, countries_by_language, or search_countries, which the name alone would have to carry.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the other country-list tools in the sibling set, and no exclusions or prerequisites. Usage is only implied by the tool name and the example regions.

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

All Countries 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