Skip to main content
Glama
Sign In

ARM Verify — Entity Intelligence API

by app.railway.up.brilliant-illumination-production-9bda
OverviewDiscussionsAdmin

verify_entity

Verify that a company is really registered, and return its official registry record. RETURNS JSON with: entity_name, jurisdiction, registration_number, status (ACTIVE / DISSOLVED / LIQUIDATION / NOT_FOUND), incorporation_date (ISO 8601, e.g. "1989-04-21"), registered_address, company_type (legal form, e.g. "Public Limited Company"), lei (20-character Legal Entity Identifier, or null if the entity has none), verification_confidence, data_sources (array of registries that answered), and notes. SOURCES: GLEIF Global LEI Index, Companies House (GB), SEC EDGAR (US), OpenCorporates, CVR (DK), BRREG (NO), PRH (FI), ARES (CZ), KRS (PL), ACRA (SG), Recherche Entreprises (FR), plus RCSL (LU), Bolagsverket (SE), Firmenbuch (AT), ABN Lookup (AU), MCA21 (IN) and CIPC (ZA). Queries the jurisdiction-specific registry first and falls back to GLEIF. USE WHEN you need to confirm a counterparty legally exists, is still active, or to resolve its LEI before onboarding. BILLING: with an API key each call is charged $1.50 from the key's credits, exactly as POST /verify (refused when the balance is too low); bank portal sessions are not charged.

Input Schema

NameRequiredDescriptionDefault
entity_nameYesFull registered company name, as close to the legal name as possible. Example: "Barclays PLC". Partial names work but reduce match confidence; omit punctuation-heavy suffixes if no result is found.
jurisdictionYesISO 3166-1 alpha-2 country code of incorporation, uppercase, exactly 2 letters. Examples: "GB" (United Kingdom), "DE" (Germany), "US" (United States), "AE" (UAE), "SG" (Singapore), "FR" (France). Determines which national registry is queried, so an accurate code materially improves results.
registration_numberNoOptional national company number, which makes the lookup exact rather than name-based. Format varies by jurisdiction. Examples: "00048839" (GB Companies House, 8 digits), "HRB 12345" (DE Handelsregister), "197401234N" (SG UEN), "552032534" (FR SIREN, 9 digits). Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / entity_name / description
      Previous value: -"Company name to verify"New value: +"Full registered company name, as close to the legal name as possible. Example: \"Barclays PLC\". Partial names work but reduce match confidence; omit punctuation-heavy suffixes if no result is found."
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"ISO 2-letter country code (e.g. GB, DE, AE, US)"New value: +"ISO 3166-1 alpha-2 country code of incorporation, uppercase, exactly 2 letters. Examples: \"GB\" (United Kingdom), \"DE\" (Germany), \"US\" (United States), \"AE\" (UAE), \"SG\" (Singapore), \"FR\" (France). Determines which national registry is queried, so an accurate code materially improves results."
    • changedInput schema / properties / registration_number / description
      Previous value: -"Company registration number (optional)"New value: +"Optional national company number, which makes the lookup exact rather than name-based. Format varies by jurisdiction. Examples: \"00048839\" (GB Companies House, 8 digits), \"HRB 12345\" (DE Handelsregister), \"197401234N\" (SG UEN), \"552032534\" (FR SIREN, 9 digits). Omit if unknown."
  2. Changed3 schema fields changed
    • addedInput schema / properties / entity_name / description
      Added value: +"Company name to verify"
    • addedInput schema / properties / jurisdiction / description
      Added value: +"ISO 2-letter country code (e.g. GB, DE, AE, US)"
    • addedInput schema / properties / registration_number / description
      Added value: +"Company registration number (optional)"
  3. Changed3 schema fields changed
    • removedInput schema / properties / entity_name / description
      Removed value: -"Company name to verify"
    • removedInput schema / properties / jurisdiction / description
      Removed value: -"ISO 2-letter country code (e.g. GB, DE, AE, US)"
    • removedInput schema / properties / registration_number / description
      Removed value: -"Company registration number (optional)"
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses billing ($1.50 per call charged from API-key credits, refused when balance is too low, bank portal sessions free), the data provenance (17 named registries), and the resolution strategy (jurisdiction-specific registry first, GLEIF fallback). This is exactly the cost/auth/source behavior an agent needs before invoking a paid external lookup.

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?

Front-loaded with purpose, then returns, sources, fallback, usage, and billing in a logical order. The 17-registry enumeration is bulky but arguably load-bearing for a jurisdiction-scoped tool, so it is defensible rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates fully by enumerating every returned field (including the status enum values and null-able LEI) plus source registries, fallback order, and billing semantics. An agent has everything needed to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining that the jurisdiction parameter selects which national registry is queried and that GLEIF is the fallback, and the SOURCES list lets the agent anticipate coverage gaps for a given country code.

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?

Opens with a specific verb and resource: 'Verify that a company is really registered, and return its official registry record.' That is clearly distinct from siblings like screen_sanctions, score_risk, and map_ownership, which involve different operations on the same entity.

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?

'USE WHEN you need to confirm a counterparty legally exists, is still active, or to resolve its LEI before onboarding' gives concrete trigger conditions. It lacks an explicit when-not statement or a named alternative among the sibling tools, so it stops short of a 5.

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

All ARM Verify — Entity Intelligence API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources