Skip to main content
Glama

Company registry timeline

company_history
Read-onlyIdempotent

Get one company's BORME timeline: its published registry events within your plan's window.

Use it once the company is known (a slug from search_companies or company_by_nif); across many companies use search_events. A name is searched too: several matches return {ambiguous: true, candidates}, none returns {error, suggested_companies}.

Returns JSON {company_slug, total_events, first_seen, last_seen, truncated, next_offset, count, events} (as in search_events), with former_slugs for a merged company (an old slug returns the merged timeline) and plan_window on a limited plan. total_events, first_seen and last_seen cover the whole timeline in your window, not this page. To page, keep limit and order and pass next_offset as offset (at most 10000) until it is null.

Read-only; one request per call. Without an API key (X-API-Key header) only the last 7 days; basic covers 365 days, pro and risk the full history back to 2009. If all its events are outside your window, the refusal counts them.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEvents per page, integer 1-200, e.g. 20 (default 100).
orderNo"desc" (default, newest first) or "asc" (oldest first), e.g. "asc" to start from the earliest event in your plan's window.desc
offsetNoEvents to skip, integer 0-10000 (default 0); pass the previous page's next_offset, e.g. 100.
companyYesCompany 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.
include_inferredNoOptional, default false, e.g. true. true allows an inferred sector on events without a CNAE code: the first act with a non-empty objeto social gets `fields` with `cnae_inferred` (a CNAE-2009 division), `cnae_source` `jev` and `cnae_inference` (`confidence`, `model`, `prompt`, `section`, `note`). Nothing is added if any act has a CNAE code, no act has a non-empty objeto social, or no decision qualifies. It is the output of a language model (TypeSafe Jev, model `typesafe-ai/jev-1.14.0`, prompt ID `two-stage-v1`), not a code published in BORME, and it describes the objeto social, not the company's verified activity. Only decisions whose confidence meets the threshold are returned (default 0.9). Inferred values are included only on request: if you omit `include_inferred` or set it to `false`, there are none. Only acts published from 2024-11-05 have inferred divisions (`note`), so more sector coverage from that date may reflect them and does not, by itself, show market growth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description adds real behavior beyond them: one request per call, the X-API-Key tier ladder (anonymous 7 days, basic 365 days, pro/risk back to 2009), merged-company former_slugs resolution, plan_window on limited plans, and the fact that out-of-window refusals still count events. It also discloses that total_events/first_seen/last_seen are timeline-wide rather than page-wide, which prevents a common misreading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The routing and pagination guidance is front-loaded and earns its place, but roughly half the text is a detailed include_inferred explanation that duplicates the schema's own description almost verbatim, plus a redundant restatement ('if you omit include_inferred or set it to false, there are none'). It is dense paragraph prose rather than structured sections, so it is informative but longer than necessary.

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?

With no output schema, the description fully enumerates the returned fields (company_slug, total_events, first_seen, last_seen, truncated, next_offset, count, events) plus the conditional former_slugs and plan_window keys, and explains scope of the aggregates and how to page. For a read-only timeline tool this covers everything an agent needs to call it and interpret the result.

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%, and the parameters are already well documented there, including pagination semantics and the long include_inferred explanation, which the description largely restates. The description adds genuine meaning only in the paging rule ('keep limit and order and pass next_offset as offset ... until it is null') and the ambiguity/unmatched return behavior for the company argument, so the baseline 3 applies.

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 opening sentence names a specific verb and resource ('Get one company's BORME timeline: its published registry events') and immediately constrains scope to a single company within the plan window. It also names the siblings it is not (search_companies, company_by_nif, search_events), so an agent can distinguish it without opening a schema.

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 an explicit precondition ('once the company is known, a slug from search_companies or company_by_nif') and an explicit alternative for the other case ('across many companies use search_events'). It also states what happens when the identifier is ambiguous or unmatched, and notes the plan-window exclusion case, so the agent knows both when to call it and what a refusal means.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.