Skip to main content
Glama
ClearStack Data MCP server

ClearStack Data MCP server

by Wordhalm

Verify EU company and VAT number

verify_eu_company
Read-only

Validate EU VAT numbers against the VIES service and return official registry records, including legal name, status, address, and officers for compliance and onboarding checks.

Instructions

Validate EU VAT numbers against the European Commission VIES service and return the official registry record (France SIRENE, Swiss Zefix, Norway Brreg, Finland PRH, GLEIF LEI): legal name, status, address, legal form, officers. Cost on the user's Apify account: $0.004 per company.

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": {
      "queries": "<queries>"
    },
    "name": "verify_eu_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesEU VAT numbers ("FR22424761419"), French SIREN/SIRET, Swiss UID ("CHE-105.909.036"), Norwegian org numbers ("NO:923609016").
defaultCountryNoISO-2 country used when a query is a plain company name.

Output Schema

NameRequiredDescriptionDefault
actorYesApify Actor that produced the data
itemsYes
runIdYesApify run ID; pass it to get_run_results if finished is false
statusYesApify run status, e.g. SUCCEEDED or RUNNING
finishedYesfalse when the run was still going and items are partial
itemCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the upstream data sources and a concrete cost of $0.004 per company on the user's account, which matters for a batched call. It stops short of noting VIES downtime behavior or what an invalid/unmatched number yields.

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?

Two sentences, front-loaded with the core action and data sources, then cost. The parenthetical registry list is long but informative rather than filler. Minor density cost from enumerating five registries inline.

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 an output schema present and 100% parameter coverage, the description only needs to add sourcing and cost context, which it does. For a read-only verification tool with a batch of up to 200 queries, the remaining gaps (invalid-number handling, failure modes, latency) are minor.

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 parameters are already documented with format examples. The 'per company' pricing wording hints that cost scales with the size of the queries array, which is a mild addition, but the description says nothing extra about defaultCountry or batch behavior. Baseline 3 applies when the schema carries the load.

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 (validate) and resource (EU VAT numbers), names the authoritative service used (European Commission VIES), and enumerates the upstream registries (SIRENE, Zefix, Brreg, PRH, GLEIF). An agent can tell exactly what this tool does and what it returns 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 Guidelines3/5

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

Usage is implied by the domain ('validate EU VAT numbers') but there is no explicit when-to-use statement, no exclusions (e.g. non-EU entities), and no guidance on choosing it over any other lookup path. The supplied siblings are unrelated, so nothing is actively misleading, but the agent must infer the trigger conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.