Skip to main content
Glama

A company's signals

company_signals
Read-onlyIdempotent

Get one company's derived signals within your plan's window, newest first: the REST API's GET /v1/companies/{slug}/signals.

Use it for one company's ownership changes, mass exits, insolvency declarations and the like; across all companies use recent_signals. A name is searched as in company_history: several matches return {ambiguous: true, candidates}, none returns {error, suggested_companies}.

Returns JSON {company_slug, total, count, next_offset, signals: [{event_id, signal_type, date, company_slug, company_name, province, details}]}, with former_slugs for a merged company (every slug is read), and plan_window or hidden_by_plan when your plan's window applied: relay their notes. AEAT_DEBTOR: say the company was on the list published on that date, never that the debt is outstanding. count 0 is not proof of good health.

Read-only; one request per call. Needs the pro plan or higher (CONSOLIDATION and PE_ENTRY: risk); 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_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSignals per page, integer 1-200, e.g. 20 (default 50).
offsetNoSignals to skip, integer 0-10000 (default 0); pass the previous page's next_offset, e.g. 50.
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 as in company_history.
date_toNoLatest signal date, inclusive, YYYY-MM-DD, e.g. 2026-10-31. Optional.
date_fromNoEarliest signal date, inclusive, YYYY-MM-DD, e.g. 2024-11-01. Optional; moved up to the start of your plan's window when earlier (plan_window says so).
signal_typesNoOptional list; each one of INSOLVENCY_FILED, ACCORDION, MASS_EXIT, OWNERSHIP_CHANGE, DISTRESS_COMBO, PHOENIX, ADDRESS_CLUSTER, AEAT_DEBTOR, PUBLIC_CONTRACT_AWARD, and on the risk plan CONSOLIDATION and PE_ENTRY, e.g. ["OWNERSHIP_CHANGE", "MASS_EXIT"]; omit for all types your plan covers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/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 the description adds substantial behavior beyond them: plan-window clipping of date_from, hidden_by_plan and plan_window notes that must be relayed, merged-company former_slugs resolution, the ambiguous-candidate and error return paths, one-request-per-call limits, and the AEAT_DEBTOR interpretation caveat plus 'count 0 is not proof of good health'. It also documents the auth mechanism (X-API-Key header).

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 verb, resource, and endpoint, then scope, return shape, and caveats in a logical order; every clause carries information. It is dense and long for a tool description, but no sentence is filler, so the length is earned rather than padded.

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 still specifies the return envelope (company_slug, total, count, next_offset, signals and their fields) and the alternative shapes (ambiguous/candidates, error/suggested_companies, former_slugs, plan_window/hidden_by_plan). Nothing an agent needs to call it correctly or interpret the result 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 the baseline is 3, but the description adds meaning the schema lacks: that an early date_from is silently moved up to the plan window start, that name input follows company_history resolution, and that signal_types membership depends on the plan tier. It does not restate limit/offset behavior, which the schema already handles.

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 ("Get one company's derived signals") plus the underlying endpoint (GET /v1/companies/{slug}/signals), and explicitly contrasts scope with the sibling recent_signals for cross-company queries. An agent can distinguish it from the other signal tools 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?

Gives an explicit when-to-use rule (one company's ownership changes, mass exits, insolvency) and names the alternative for the other case (recent_signals across all companies). It also states the plan prerequisite (pro plan or higher, with per-type tiers) and that name resolution behaves as in company_history, which is exactly the routing information needed.

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.