Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

US VWP and UK visa-national list lookup

public-infrastructure_visa-waiver-list-lookup
Read-onlyIdempotent

Check whether a nationality appears on the DHS Visa Waiver Program or UK VN 1.1(a) lists. Price $0.01 USDC. POST /api/v1/public-infrastructure/visa-waiver-list-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": {
      "nationality": "<nationality>"
    },
    "name": "public-infrastructure_visa-waiver-list-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNolist, string, one of us-vwp, uk-visa-national, both. Required.both
nationalityYesnationality, string, length 2 to 100. Required.

Output Schema

NameRequiredDescriptionDefault
usVwpNousVwp. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.
nationalityNonationality. String.
ukVisaNationalNoukVisaNational. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavior, so the bar is lower. The description goes beyond them by disclosing the payment model ($0.01 USDC), the transport (POST /api/v1/...), and the crucial failure mode that an unpaid call returns x402 payment terms without executing. It adds no return-value detail, but an output schema exists.

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 compact, front-loaded sentences: purpose first, then price, then endpoint and the unpaid-call caveat. Nothing is padded, though restating the URL path verbatim is modest redundancy that could have carried the x402 note alone.

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 two parameters, full schema coverage, rich annotations, and an output schema, the description covers the essentials an agent needs: what it checks, what it costs, and what happens if payment is absent. Only the absence of any guidance on qualifying-list distinctions or result interpretation keeps it short of a 5.

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 description coverage is 100%, so both nationality and the list enum are already documented in the schema. The description hints at the two lists behind the enum but adds no format, normalization, or casing guidance for the free-text nationality field. Baseline 3 is appropriate.

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 (check) plus the exact resources it queries: the DHS Visa Waiver Program list and the UK VN 1.1(a) list. This is concrete enough to distinguish it from a nearby sibling like travel-advisory-lookup, which concerns advisories rather than visa-waiver eligibility.

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?

The use case is implied clearly enough to infer when to call it, but the description never states exclusions or points to an alternative tool. There is no 'use this instead of X when...' routing, which is what a 4 or 5 would require.

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