Skip to main content
Glama

country_support

Read-only

Return features + compliance frameworks available per supported country (187 country hubs, with detailed rows for AU, IN, GB, US, CA, AE, SG, NZ). Pass a country for one country’s full detail. The full unfiltered matrix is large, so for "which countries are supported?" pass summary: true to get a compact per-country index (feature/compliance counts) and then drill into a specific country.

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": "country_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoSingle ISO country code. Omit for the full matrix.
summaryNoWhen true and no `country` is given, return a compact per-country index (feature/compliance counts instead of the full detail) to save context. Then call with a `country` for full detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / summary
      Added value: +{
      +  "description": "When true and no `country` is given, return a compact per-country index (feature/compliance counts instead of the full detail) to save context. Then call with a `country` for full detail.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "IN",
      -  "US",
      -  "CA",
      -  "GB",
      -  "AU",
      -  "AE",
      -  "SG",
      -  "NZ"
      -]New value: +[
      +  "IN",
      +  "US",
      +  "GB",
      +  "AU",
      +  "AE",
      +  "CA",
      +  "SG",
      +  "NZ",
      +  "HK",
      +  "DE",
      +  "FR",
      +  "NL",
      +  "ES",
      +  "IT",
      +  "JP",
      +  "KR",
      +  "SA",
      +  "IE",
      +  "ZA",
      +  "MY",
      +  "PH",
      +  "NG",
      +  "KE",
      +  "ID",
      +  "TH",
      +  "VN",
      +  "PK",
      +  "BD",
      +  "BR",
      +  "MX",
      +  "AR",
      +  "CL",
      +  "CO",
      +  "SE",
      +  "NO",
      +  "DK",
      +  "FI",
      +  "BE",
      +  "AT",
      +  "CH",
      +  "PL",
      +  "PT",
      +  "CZ",
      +  "RO",
      +  "HU",
      +  "GR",
      +  "TR",
      +  "UA",
      +  "IL",
      +  "EG",
      +  "BG",
      +  "HR",
      +  "SI",
      +  "SK",
      +  "LT",
      +  "LV",
      +  "EE",
      +  "RS",
      +  "MA",
      +  "QA",
      +  "KW",
      +  "JO",
      +  "OM",
      +  "BH",
      +  "TN",
      +  "DZ",
      +  "GH",
      +  "TZ",
      +  "UG",
      +  "ET",
      +  "ZM",
      +  "ZW",
      +  "RW",
      +  "SN",
      +  "LK",
      +  "NP",
      +  "MM",
      +  "KH",
      +  "LA",
      +  "PE",
      +  "EC",
      +  "BO",
      +  "PY",
      +  "UY",
      +  "CR",
      +  "PA",
      +  "GT",
      +  "DO",
      +  "KZ",
      +  "UZ",
      +  "BY",
      +  "MD",
      +  "BA",
      +  "MK",
      +  "AL",
      +  "LB",
      +  "IQ",
      +  "TT",
      +  "MO",
      +  "BN",
      +  "CY",
      +  "MT",
      +  "LU",
      +  "IS",
      +  "ME",
      +  "GE",
      +  "AM",
      +  "AZ",
      +  "TM",
      +  "TJ",
      +  "KG",
      +  "MN",
      +  "CI",
      +  "CM",
      +  "TG",
      +  "BJ",
      +  "BF",
      +  "ML",
      +  "SL",
      +  "LR",
      +  "GN",
      +  "MR",
      +  "NE",
      +  "TD",
      +  "CD",
      +  "CG",
      +  "GA",
      +  "MW",
      +  "MZ",
      +  "NA",
      +  "BW",
      +  "LS",
      +  "SZ",
      +  "MG",
      +  "AO",
      +  "MU",
      +  "SC",
      +  "CV",
      +  "HN",
      +  "SV",
      +  "NI",
      +  "JM",
      +  "BB",
      +  "GY",
      +  "SR",
      +  "FJ",
      +  "PG",
      +  "HT",
      +  "BS",
      +  "VE",
      +  "IR",
      +  "AF",
      +  "SY",
      +  "YE",
      +  "LY",
      +  "SD",
      +  "SO",
      +  "CU",
      +  "KP",
      +  "TW",
      +  "PS",
      +  "ER",
      +  "DJ",
      +  "SS",
      +  "CF",
      +  "GQ",
      +  "BI",
      +  "KM",
      +  "ST",
      +  "GW",
      +  "EH",
      +  "WS",
      +  "TO",
      +  "VU",
      +  "SB",
      +  "KI",
      +  "TV",
      +  "NR",
      +  "PW",
      +  "FM",
      +  "MH",
      +  "AG",
      +  "LC",
      +  "VC",
      +  "KN",
      +  "DM",
      +  "GD"
      +]
  3. First observed

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 the important behavioral caveat that the unfiltered matrix is large and may blow up context, plus the recommended drill-down sequence — real operational context beyond structured fields, though it says nothing about response shape or size limits per call.

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?

Three sentences, front-loaded with what is returned, then the two usage modes. Efficient overall, though the summary/drill-down advice partially restates the schema's own parameter descriptions.

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 description does the work of indicating return shape — per-country feature/compliance rows versus a compact counts index — which is enough for an agent to call it correctly. A hint about whether all 187 hubs are equally detailed in the summary index would close the remaining gap.

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%, and the schema already describes both parameters, including "Single ISO country code. Omit for the full matrix" and the summary flag's purpose. The description reinforces the intended two-step workflow (summary first, then drill into a country) but adds little syntactic or semantic detail the schema lacks.

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 states a specific verb and resource ("Return features + compliance frameworks available per supported country") and quantifies scope (187 country hubs, with detailed rows for AU, IN, GB, US, CA, AE, SG, NZ). An agent knows exactly what data domain this covers without opening the 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?

It gives explicit routing for the two internal modes: pass `country` for one country's full detail, or `summary: true` for the compact index when answering "which countries are supported?". It does not name or disambiguate sibling tools such as compliance_capabilities or feature_search, so cross-tool selection is left to inference.

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