Skip to main content
Glama

Business Check - EU VAT, company address, domain age, risk flags

business_check
Read-onlyIdempotent

One-call KYB check of a company: EU VAT number validated in the official VIES register (company name and registered address), the address geocoded by the national geocoder, the website domain's age and registrar (RDAP), its email authentication score, and plain risk flags (invalid VAT, domain younger than 180 days, name not matching the domain, spoofable email). ~1-2 s. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/business-check.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "google.com",
      "vatNumber": "IE6388047V"
    },
    "name": "business_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoCompany website or e-mail domain, e.g. google.com
addressNoOptional address to geocode instead of the registered one
vatNumberNoEU VAT number with country prefix, e.g. IE6388047V (also NO/CH/GB formats)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the description earns credit for the operational details annotations cannot carry: ~1-2 s latency, a 25 calls/day per IP free tier, and $0.01 per call paid access via x402. It stops short of saying what happens when the free quota is exhausted or whether partial results are returned when one sub-check fails, which matters for a multi-source aggregator.

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?

Purpose, checks performed, risk-flag semantics, latency and pricing are all front-loaded and every element is useful. The middle section is a dense run-on list, but no sentence is padding.

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?

With no output schema, the description must convey return content, and it does list what comes back (validated name and address, geocode, domain age and registrar, email auth score, plain risk flags) plus cost and rate limits. It still leaves response shape, error behavior for invalid VAT numbers, and the minimum viable parameter combination unstated, which is a gap for an aggregator of this complexity.

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 the schema already explains all three parameters, including VAT country-prefix formats and the optional address override. The description reinforces that the address parameter replaces the registered-address geocode, but adds no syntax or format detail beyond the schema, and notably does not clarify the behavior with zero required parameters (e.g. whether domain alone is sufficient).

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?

The description names a specific verb and resource ('One-call KYB check of a company') and enumerates exactly which sub-checks it aggregates: VIES VAT validation, geocoding, RDAP domain age/registrar, email authentication score, and risk flags. This lets an agent distinguish it from single-purpose siblings like email_auth or domain_intel without opening the schema.

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

Usage Guidelines4/5

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

The 'one-call' framing makes the intended context clear: use this when you want a bundled KYB assessment rather than several individual lookups. However, it never explicitly names the sibling tools or says when NOT to use this broader, costlier call in favor of a narrower one, so guidance is strong but not complete.

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