BORME API - Spain company registry

Company registry card

company_snapshot

Read-onlyIdempotent

Get one company's current registry card: the same answer as the REST API's GET /v1/companies/{slug}.

Use it for "who runs it, who owns it, what capital": officers (the current roles derived from the published acts), sole_shareholder as printed, capital_eur, address, status, NIF with its source, public_contracts and a size_hint estimate. For the dated acts use company_history. A name is searched as in company_history: several matches return {ambiguous: true, candidates, candidate_names with name, province and status}, none returns {error, suggested_companies}.

Returns JSON with company_slug, company_name, current_name, status, officers, sole_shareholder, capital_eur, nif, nif_caveat, sources and the other snapshot fields, plus former_slugs for a merged company. BORME publishes no minority shareholdings, employees or revenue.

Read-only; one request per call. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).

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": {
      "company": "<company>"
    },
    "name": "company_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`company`	Yes	Company slug, e.g. vaz-metales-sl (from search_companies), or a name of at least 3 letters or digits, e.g. "Mercadona", searched case-insensitively as in company_history.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only and idempotence annotations, it discloses derived officer roles, printed sole_shareholder values, the estimated size_hint, ambiguity and error payloads, former_slugs for merged companies, and BORME's lack of minority shareholdings, employees, and revenue. It also adds one-request-per-call behavior and the basic-plan and X-API-Key requirements.

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?

The description is front-loaded and organized into purposeful paragraphs covering scope, lookup behavior, results, limitations, and access. It is mildly repetitive because fields such as officers, sole_shareholder, capital_eur, and status appear in both the capability and return-field lists, while "Read-only" repeats the annotations.

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?

For a one-parameter read tool without an output schema, it supplies the snapshot scope, sibling alternative, lookup outcomes, representative JSON fields, merged-company handling, source limitations, request cardinality, and authentication requirements. This is sufficient for an agent to select, invoke, and interpret the tool without important undocumented gaps.

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?

The schema already fully documents the company argument, including slug and name forms, minimum name length, and case-insensitive search. The description adds useful meaning by explaining how a name argument resolves into either ambiguous candidates with province and status or an error with suggested_companies, though it adds little new input syntax.

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 uses a specific verb and resource: "Get one company's current registry card," and identifies the equivalent REST endpoint. The "who runs it, who owns it, what capital" scope and the contrast with company_history clearly distinguish this current snapshot from dated-act retrieval.

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

Usage Guidelines5/5

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

It gives explicit positive guidance with "Use it for" and names an alternative with "For the dated acts use company_history." It also explains the multiple-match and no-match paths for name searches, helping the agent anticipate when disambiguation or another lookup step is needed.

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

All BORME API - Spain company registry tools Inspect

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

Need Help?