Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Spanish company acts (BORME)

get_spanish_company_acts
Read-only

Fetch official BORME company acts by Spanish hoja registral key from search_european_companies to review incorporations, officer changes, capital events, mergers, dissolutions, and insolvency.

Instructions

Spanish company acts from the official BORME gazette (Registro Mercantil, section A) by hoja registral, the register key (e.g. VI-23141) returned by search_european_companies for Spain: incorporations, officer appointments and dismissals (role + name), capital changes, mergers, dissolutions, insolvency. Daily flow since 2009, newest first (100 max + total count). Spanish personal IDs (DNI/NIE) and natural-person sole-shareholder names are redacted at ingestion, marked « […] ». The hoja of a sole trader (a BORME empresario individual act) returns 404, not billed; so does a hoja whose name carries no company legal form from the closed Spanish list (forme_juridique_non_servie: the name may be a sole trader's civil name). A company with a current name under objection (GDPR art. 21) returns the same 404 as an unknown hoja, not billed; an act's denomination under objection is served null and counted in ecartes.opposition (item kept, block partial in provenance). Basado en datos de la Agencia Estatal Boletín Oficial del Estado. Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

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": {
      "hoja": "<hoja>"
    },
    "name": "get_spanish_company_acts"
  }
}

Input Schema

NameRequiredDescriptionDefault
hojaYesHoja registral (register-sheet key), e.g. VI-23141, from search_european_companies with pays=ES. The BORME does not publish the NIF.

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, yet the description adds substantial behavior: daily flow since 2009, newest-first ordering, 100-result cap plus total count, DNI/NIE and sole-shareholder redaction marked « […] », 404-not-billed semantics, null denomination with ecartes.opposition for objected names, and x402 pricing at $0.02. This is exactly the kind of context annotations cannot carry.

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?

Dense but front-loaded: the resource and key are stated first, then coverage, then edge cases and billing. Every sentence carries operational information, though the GDPR/ecartes sentence is packed tightly enough to require a second read.

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 single-parameter read tool with an output schema, the description covers everything an agent needs: where the key comes from, what acts are returned, ordering and limits, redaction, error semantics, billing, and the citation requirement. Nothing material is left to inference.

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% and the single parameter already documents the hoja format, so the baseline is 3. The description adds real value by stating the key comes from search_european_companies with pays=ES and that BORME does not publish the NIF, which prevents an agent from trying to look the company up by tax ID.

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?

States a specific verb and resource ('Spanish company acts from the official BORME gazette ... by hoja registral') and enumerates the act types covered (incorporations, officer appointments, capital changes, mergers, dissolutions, insolvency). It also names the sibling that produces the required key (search_european_companies with pays=ES), so an agent can distinguish it from other Spanish tools.

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?

Gives a clear prerequisite (the hoja key must come from search_european_companies for Spain) and explains the main failure modes: sole-trader hoja, names without a legal form, and GDPR art. 21 objections all return 404 and are not billed. It does not explicitly contrast with other Spanish siblings like get_spanish_company_public_procurement, but the resource is distinct enough that this is a minor gap.

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

Deploy Server

Other Tools