Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Country Lookup

CountryLookup
Read-only

Country Lookup: Country Lookup matches any country name or ISO code to its official names, ISO 3166 codes, capitals, region, languages, and flag emoji. Paid plans add coordinates and major cities, and with details=true demonyms, land area and UN membership. (Cost: 2 credits)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "CountryLookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesThe Country name or ISO code of the country for which you want to get the data (e.g., USA)
detailsNoSet to true to add demonyms, land area in square kilometers, and UN membership to each country
majorcitiesNoSpecify if you would like to return all major cities of the country found

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious context the annotations cannot: a 2-credit cost, and tier gating where coordinates and major cities require a paid plan and details=true unlocks extra fields. It does not say what happens when the identifier fails to match.

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?

A single dense sentence block that front-loads the core capability, then the optional enrichments, then cost. No filler beyond the mild redundancy of restating the tool title at the start.

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 an output schema present it need not describe return values, and the annotations cover safety. Cost, tier gating and the details toggle are all disclosed, leaving only edge-case behavior for unmatched or ambiguous country inputs unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies, but the description goes further by tying details=true to specific extra fields and by revealing that majorcities is gated behind a paid plan, information absent from the schema. The 'country' parameter's accepted forms (name or ISO code) are restated rather than extended.

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?

Names a specific resource (country) and enumerates exactly what it resolves: official names, ISO 3166 codes, capitals, region, languages and flag emoji. That field list distinguishes it from nearby siblings such as CountryFlags, CountryLanguages and CountryBorders without the agent needing to open 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 Guidelines3/5

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

Implied usage only: the agent can infer it is the right tool when it needs combined country attributes rather than a single-attribute lookup. There is no explicit statement of when to prefer CountryFlags or CountryLanguages instead, and no mention of error behavior for an ambiguous or unknown country string.

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

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