Skip to main content
Glama

Registry events of the identified sole-shareholder network

group_history
Read-onlyIdempotent

Get the BORME events of every company in the identified sole-shareholder network (as company_group returns it), newest first, within your plan's window.

Use it before a visit ("which BORME events were published this year for companies in X's identified sole-shareholder network") or for the published mergers, demergers and capital changes concerning companies in the identified network; for one company use company_history. A name is searched as in company_group.

Returns JSON {company_slug, members, member_count, group_truncated, count, offset, next_offset, events: [{event_id, date, borme_id, province, company_name, company_slug, member_slug, acts, registral}]}, with plan_window on a limited plan. member_slug is the group member the event belongs to. To page, pass next_offset as offset until it is null.

Read-only. Needs the pro plan (X-API-Key header).

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": "group_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEvents per page, integer 1-200, e.g. 20 (default 50).
offsetNoEvents to skip, integer 0-10000 (default 0); pass the previous page's next_offset.
companyYesCompany slug, e.g. vaz-metales-sl, or a name of at least 3 letters or digits; its whole group is read.
date_toNoLatest publication date, inclusive, YYYY-MM-DD. Optional.
act_typesNoOptional list of act type enums, e.g. ["MERGER_BY_ABSORPTION", "SEGREGATION"]. Full list: list_act_types.
date_fromNoEarliest publication date, inclusive, YYYY-MM-DD, e.g. 2025-01-01. Optional; moved up to your plan's window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's 'Read-only' line is redundant. What it does add beyond annotations is valuable: pro plan requirement with X-API-Key header, plan-window truncation (plan_window, group_truncated), and the paging loop via next_offset. Return shape and pagination behavior are well disclosed, though the plan-window semantics are only named, not explained.

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 the core action and scope, then usage, then return shape and paging. The inline return-object listing is long but justified since there is no output schema; minor redundancy in restating 'Read-only' and repeating the network qualifier several times.

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 supplies the full response envelope (company_slug, members, member_count, count, offset, next_offset, events fields) and the member_slug meaning, plus auth tier and paging termination condition. Nothing an agent needs to call and page correctly is missing.

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 baseline is 3; the description still adds meaning by explaining the paging protocol ('pass next_offset as offset until it is null') and that date_from is clamped to the plan window, which the schema only hints at with 'moved up to your plan's window'.

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?

Names a specific verb and resource (BORME events of every company in the identified sole-shareholder network), states ordering (newest first) and scope limit (plan window), and explicitly distinguishes itself from company_group (which supplies the network) and company_history (single company).

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?

Gives concrete when-to-use cases (pre-visit checks, published mergers/demergers/capital changes) and an explicit when-not/alternative rule: 'for one company use company_history'. It also clarifies the input convention ('A name is searched as in company_group'), removing ambiguity about accepted identifiers.

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.