Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-capital-city

Capital City: Fetches a country's capital from the countriesnow API by country name, returning country and capital fields 🆓 5 free trial calls per signed wallet

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": "x402-capital-city"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
inputNo
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / country / description
      Removed value: -"Country to process"
    • removedInput schema / properties / input / description
      Removed value: -"Input to process"
    • removedInput schema / properties / name / description
      Removed value: -"Name to process"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the data source and the return fields, and adds a real behavioral fact ('5 free trial calls per signed wallet'), implying wallet signing and a quota. It omits what happens on an unknown country, error behavior, and whether results are cached.

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?

One compact sentence that front-loads the action and resource, followed by the pricing/quota note. The 'Capital City:' prefix duplicates the tool name and slightly wastes the opening, but nothing else is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup with no output schema, the description does cover the return shape ('country and capital fields') and the pricing model, which is helpful. The unresolved ambiguity among `name`, `input`, and `country` is the remaining gap an agent would hit when actually calling it.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters. The description only clarifies 'by country name', plausibly mapping to the `country` field, while `name` and `input` remain entirely undefined in both schema and description — the agent cannot tell whether they are aliases or distinct inputs.

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 ('Fetches a country's capital ... by country name') plus the upstream source (countriesnow API) and the returned fields. This distinguishes it from nearby siblings like x402-country, x402-country-code, and x402-currency-by-country, though it never names an alternative explicitly.

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 input ('by country name'), so an agent can infer when to call it, but there is no when-not guidance and no routing to sibling tools that cover related lookups (currency, language, country-code for the same country).

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.