Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

US and UK travel advisory lookup

public-infrastructure_travel-advisory-lookup
Read-onlyIdempotent

Return State Department and FCDO travel advice for a country side by side. Price $0.02 USDC. POST /api/v1/public-infrastructure/travel-advisory-lookup. An unpaid call returns the x402 payment terms and does not run.

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": "public-infrastructure_travel-advisory-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYescountry, string, length 2 to 100. Required.

Output Schema

NameRequiredDescriptionDefault
ukNouk. Object.
usNous. Object.
countryNocountry. String.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.02 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without executing. Return value details are covered by the existing output schema.

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?

Three short sentences, front-loaded with the purpose, then price, then failure semantics. The endpoint path is the only borderline item and earns its place by identifying the x402-paid resource.

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?

A simple single-parameter lookup with an output schema and rich annotations; the description covers the payment gate, which is the main thing annotations cannot express. Minor gaps remain around country identifier format and unsupported-country behavior, but nothing essential to invoking it is missing.

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%, so the single 'country' parameter is already documented, giving a baseline of 3-4. However, the description does not resolve the real ambiguity in that schema (country name vs ISO code, despite a 2-character minimum), so it adds no meaning beyond the structured field.

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?

States a specific verb and resource ('Return State Department and FCDO travel advice for a country') and adds the distinguishing scope 'side by side', making the dual-source output immediately clear. No sibling covers travel advisories, so the tool is unambiguous among the listed alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description never says when to use this versus alternatives, nor any preconditions such as supported country formats or coverage gaps. The only guidance is operational (payment behavior), which is behavioral rather than usage guidance.

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