Skip to main content
Glama

countries

by io.github.pipeworx-io

Countries By Language

countries_by_language
Read-onlyIdempotent

Find countries where a language is spoken (e.g., "Spanish", "Mandarin"). Returns name, capital, region, population, and official language status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageYesLanguage name (e.g. "spanish", "french", "arabic")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of countries speaking the language
languageYesLanguage name queried
countriesYesCountries where language is spoken, sorted by population descending

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of countries speaking the language",
+      "type": "integer"
+    },
+    "countries": {
+      "description": "Countries where language is spoken, sorted by population descending",
+      "items": {
+        "properties": {
+          "capital": {
+            "description": "Capital city or N/A if not available",
+            "type": "string"
+          },
+          "name": {
+            "description": "Common country name",
+            "type": "string"
+          },
+          "population": {
+            "description": "Total population",
+            "type": "integer"
+          },
+          "region": {
+            "description": "Geographic region",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "capital",
+          "region",
+          "population"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "language": {
+      "description": "Language name queried",
+      "type": "string"
+    }
+  },
+  "required": [
+    "language",
+    "count",
+    "countries"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "language": "spanish"
+  },
+  {
+    "language": "mandarin"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds context about the return payload (name, capital, region, population, official language status), which goes beyond the annotation hints. No contradiction.

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 a single sentence that front-loads the action and resource, then specifies expected outputs. Every word contributes, with no fluff.

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 one parameter, a complete schema, and an output schema, the description sufficiently covers the tool's behavior and return values. No additional context is needed for a simple lookup tool.

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% with a clear parameter description and examples. The tool description's examples ('Spanish', 'Mandarin') are redundant with the schema, so it does not add significant additional meaning beyond the baseline.

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 uses a specific verb ('Find') and clearly identifies the resource ('countries') and the filtering criterion ('where a language is spoken'). It also lists the returned fields, making it distinct from sibling tools like countries_by_currency or countries_by_region.

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 clearly implies the use case: when you need countries for a given language. It gives examples but does not explicitly mention alternatives or exclusion scenarios, so it falls short of a 5.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

The tool set is a mix of country lookups and many unrelated Pipeworx tools (e.g., prediction markets, memory, subscriptions). While the country-specific tools are distinct, the overall set is a hodgepodge, making it difficult for an agent to determine which tools are relevant to a given task.

Naming Consistency2/5

Naming conventions are mixed: some use verb_noun (search_countries), some noun_verb (countries_by_currency), some single verbs (forget, recall), and some phrases (ai_visibility_check, ask_pipeworx). No consistent pattern is followed.

Tool Count1/5

35 tools is excessive for a server named 'countries'. Only about 6-7 tools are actually related to countries; the rest are unrelated (Pipeworx services, prediction markets, etc.), creating an extreme mismatch between the server name and its content.

Completeness2/5

For the country domain, the tool set includes search and lookups by code/currency/language/region but lacks basic CRUD, comparisons, maps, or sorting. Additionally, the presence of many unrelated tools dilutes completeness for the stated purpose.

Resources