Skip to main content
Glama

Locate BORME Section I acto-inscripción entries for a Spanish company

list_actos_inscritos
Read-onlyIdempotent

Search BORME-A province PDFs for statutory registered acts of a specific company (by exact denominación social). Retrieve director appointments, resignations, capital changes, dissolution, and other inscritos acts not available through standard company search.

Instructions

Scans BORME Section I (Empresarios — Actos inscritos) and Section B (Otros actos) province PDFs across a date range, returns every acto paragraph whose header line exactly matches the given denominación. Use this to recover current/historical directors, resignations, constitución details, sole-shareholder declarations, capital changes, dissolution, extinción — all statutory registered acts, which are NOT exposed by the per-company /buscar/anborme.php search (that indexes only Section II Anuncios y avisos legales).

Each hit includes the verbatim acto_numero (BOE's in-year sequential), borme_a_id (BORME-A-YYYY-NNN-PP province bulletin), provincia title, source_pdf_url, pagina_inicial/final, denominacion_upstream (as printed, including accent/punctuation drift), and texto_raw — the complete paragraph text from the {Nº} - {DENOMINACIÓN}. header to the next acto boundary. The adapter does NOT parse specific fields (Nombramientos / Ceses / Socio único / Capital / Datos registrales) — read texto_raw and extract inline.

Performance: each day in the range costs ~N province PDF fetches (N ≤ 52 provinces but typically 20–40). Default window: last 30 days. Hard cap: 90 days per call. Chunk longer windows client-side. Supported on ES only. Cached on the VM (PDFs are immutable once published).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdictionYes'ES' only.
company_idYesExact denominación social as emitted by the BORME header line — legal-form suffix required (e.g. 'ALICANTE PARK SL.', 'TELEFÓNICA, S.A.', 'REPSOL, S.A.'). Matching is accent-insensitive and treats '.', ',', and whitespace as interchangeable separators, but it is NOT substring matching — 'FOO SL' will not match 'FOO HOLDING SL'. Call search_companies first to obtain the canonical form surfaced in recent Section II publications.
date_fromNoStart of the scan window, ISO YYYY-MM-DD. Defaults to 30 days before today.
date_toNoEnd of the scan window, ISO YYYY-MM-DD. Defaults to today.
limitNoMax acto entries to return (default 50, max 200).
cursorNoPagination cursor from a previous response.
act_typesNoPre-filter acto paragraphs by canonical act-type key (or raw Spanish verbatim substring). Supported keys: 'nombramiento', 'cese', 'dimision', 'revocacion', 'adm-unico', 'liquidador', 'apoderado', 'poderes', 'consejero', 'auditor', 'socio-unico', 'unipersonalidad', 'ampliacion-capital', 'reduccion-capital', 'capital', 'constitucion', 'disolucion', 'extincion', 'transformacion', 'modificacion-estatutos', 'cambio-denominacion', 'cambio-domicilio', 'cambio-objeto-social', 'fusion', 'escision', 'cesion-global', 'concurso', 'prorroga'. Unrecognised keys are treated as case/accent-insensitive Spanish substring match against texto_raw (power-user escape hatch).
province_filterNoRestrict the scan to these BORME-A province codes (2-digit PP suffix of 'BORME-A-YYYY-NNN-PP'; e.g. '03'=Alicante, '28'=Madrid, '08'=Barcelona). Empty → adapter consults its per-company province cache, falling back to all provinces on miss. Use this when you already know the company's Registro Mercantil.
bypass_province_cacheNoDisable the per-company province cache for this call. Useful when a company has moved domicilio and previous cache would miss new actos.
freshNoBypass the PDF extraction and sumario caches.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queried_atYesISO-8601 + Europe/London timezone stamp for when the registry was queried.
jurisdictionNo
company_idNo
countNo
actosNo
dataNo
Behavior5/5

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

Annotations idempotentHint and readOnlyHint already indicate safe read operations; description adds crucial behavioral details: performance cost (N province PDFs per day), default window, hard cap, caching behavior, and the fact that PDFs are immutable. It also notes adapter does not parse specific fields, directing the agent to read texto_raw. No contradiction with annotations.

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 comprehensive and well-organized, with a clear first sentence summarizing the core function, followed by usage guidance, output details, and performance notes. It is slightly long but every sentence adds value. Could be trimmed slightly without losing clarity.

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?

Given the complexity (10 parameters, output schema exists, no sibling ambiguity for this specific function), the description is complete. It covers purpose, alternatives, parameter semantics, performance, cache, and output shape. The rich annotations and output schema reduce the burden, and the description fills all remaining gaps.

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

Parameters5/5

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

Schema coverage is 100% yet the description adds significant value for each parameter: for company_id it explains matching rules (accent-insensitive, not substring), for act_types it lists supported keys and mentions power-user substring fallback, and for province_filter it describes cache behavior. This enriches the schema beyond type/format constraints.

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 clearly states the tool scans BORME Section I and B data across PDFs to retrieve statutory registered acts by exact denominación, and distinguishes its behavior from the per-company search (which only indexes Section II). The verb 'scans' accurately conveys the resource and action.

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?

Explicitly states when to use this tool (to recover historical statutory acts not available via other search) and when not to use it (by mentioning the per-company /buscar/anborme.php only indexes Section II). It also advises calling search_companies first for canonical denominación and gives performance and caching guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sophymarine/openregistry'

If you have feedback or need assistance with the MCP directory API, please join our Discord server