Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Country Flags

CountryFlags
Read-only

Country Flags: Country Flags is a country flag API that fetches direct download URLs for national flag images using two-letter ISO country codes. Responses return the country name, ISO code, and image link, while paid plans can select SVG or PNG formats and shapes. (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": "CountryFlags"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeNoThe shape of the flag image: rectangle (official proportions), square (1:1 icon) or circle (round 1:1 icon). Optional; defaults to rectangle.
formatNoThe format of the flag image. Optional; defaults to png.
countryYesThe 2 letter ISO Country Code (e.g. ZW)

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

A3.7/5.0
Behavior4/5

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

With annotations already covering read-only, open-world, and non-destructive behavior, the description adds useful context about the 2-credit cost and paid-plan gating for SVG/PNG and shape options. It also states the response fields, though it does not describe error behavior for invalid country codes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately short, but it opens with redundant repetition: "Country Flags: Country Flags is a country flag API." The remaining content is efficient and front-loads the core purpose.

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 low-complexity image URL lookup with an output schema and safety annotations, the description covers the essential purpose, return fields, cost, and plan-dependent options. It is complete enough to call correctly, with only minor gaps around failure behavior.

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 the baseline is 3, but the description adds meaningful context beyond the schema by noting that format and shape selection are paid-plan capabilities. This helps an agent understand that optional parameters may depend on plan access.

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?

The description states a specific verb and resource: fetching direct download URLs for national flag images by two-letter ISO country code. It is clear what the tool returns, but it does not explicitly distinguish itself from nearby country-data siblings such as CountryLookup.

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?

Usage is implied by the purpose: call this when you need a flag image URL for a country. There is no explicit when-not guidance and no named alternative for related country information tasks.

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