Skip to main content
Glama

BRAINIAC Company Intelligence

Look up VAT ID and registry numbers

company-intelligence_vat-id-lookup

Validate a supplied EU VAT ID with VIES and/or search GLEIF by company name for official registration numbers. Does not invent a VAT ID when VIES has none, and does not call UK Companies House. Price $0.04 USDC. POST /api/v1/company-intelligence/vat-id-lookup. Unpaid calls return 402 and do not run.

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": "company-intelligence_vat-id-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
vatIdNo
countryNo
companyNameNo

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 no annotations, the description carries the full load and does well: it discloses cost ($0.04 USDC), the payment gating behavior (402 and no execution when unpaid), and two negative behaviors (will not fabricate a VAT ID, will not query UK Companies House). It stops short of auth requirements beyond payment and rate limits.

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?

Purpose is front-loaded in the first sentence, followed by exclusions, pricing, and transport details. Every sentence carries new information, and the repetition between the price and the 402 note is minor.

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?

No output schema exists, and the description says nothing about what a successful response contains (VIES validity status, registration number formats, GLEIF entity fields), which leaves the return shape underspecified. Cost, failure mode, and scope are otherwise adequately covered.

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 0%, so the description must compensate. It gives meaning to vatId (EU VAT ID, VIES) and companyName (GLEIF search key), but leaves `limit` and `country` completely unmentioned, so two of four parameters remain undocumented anywhere.

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 names two concrete verbs and resources: validate an EU VAT ID via VIES, and search GLEIF by company name for registration numbers. It is clearly distinct from filings/financials/profile siblings by scope, though it does not explicitly contrast with them (it only rules out UK Companies House, which is not a sibling).

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 'and/or' phrasing implies mode selection based on which input you have (vatId for VIES, companyName for GLEIF), but the choice is never stated explicitly as a when-to-use rule. There is no guidance on which sibling tool to pick for other company-data needs.

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