Skip to main content
Glama

Recent risk signals

recent_signals
Read-onlyIdempotent

Get a sample of the latest risk signals derived from BORME and public sources: at most 10 rows dated within the last 7 days.

Use it for "what risk signals appeared this week"; not a per-company check (use company_history) and not the full feed (the hosted API's /v1/signals).

Returns JSON {count, window, sample_cap, signals: [{signal_type, date, company_slug, company_name, province, details}], full_feed}. AEAT_DEBTOR comes from the AEAT's yearly debtors list (art. 95 bis LGT): details carry listed_on, list_year, is_current_list (true for 12 months from listed_on) and debt_eur, the published total at 31 December of the prior year. Say the company was on the list published on that date; never say the debt is still outstanding. count 0 means none in the window, not that a company is risk-free; an unknown signal_type is refused with the valid list.

Read-only; one request per call. Needs the risk plan: send your API key in the X-API-Key header (https://bormeapi.com/account).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
signal_typeNoOptional, one of INSOLVENCY_FILED, ACCORDION, MASS_EXIT, OWNERSHIP_CHANGE, DISTRESS_COMBO, PHOENIX, ADDRESS_CLUSTER, AEAT_DEBTOR, PUBLIC_CONTRACT_AWARD, CONSOLIDATION (a merger, segregation or global transfer), PE_ENTRY (a possible investment vehicle or manager, by name, becomes sole shareholder or director; re-elections are excluded, and a director appointment does not raise it if the entity already has an overlapping director or sole-shareholder link to that company), e.g. MASS_EXIT; omit for all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world, non-destructive), the description discloses the sample cap, the time window, one-request-per-call behavior, and the authentication requirement including the header name and plan needed. It also adds interpretation guardrails for AEAT_DEBTOR (report the publication date, never claim the debt is still outstanding) and clarifies that count 0 means nothing in the window rather than a clean company — behavior no annotation covers.

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 purpose, scope, and the negative routing in the first two sentences, then return shape, then caveats. Dense but nearly every sentence carries operational information; the AEAT_DEBTOR paragraph is long, though it earns its place with interpretation guidance not available elsewhere.

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?

There is no output schema, and the description compensates by spelling out the returned JSON shape and field list, plus the special-case fields for AEAT_DEBTOR. Auth requirements, scope limits, and error behavior are all present, leaving nothing an agent needs in order to call this correctly.

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 single parameter already carries the full enumerated value list with per-value explanations, so the schema does the heavy lifting. The description adds only one genuinely new semantic — an unknown signal_type is refused with the valid list — which is useful but modest at this coverage level.

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 a sample of the latest risk signals'), plus the two constraints that define the result set: at most 10 rows and dated within the last 7 days. It explicitly distinguishes itself from the per-company check (company_history) and from the full feed, so an agent can place it without opening any 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 a concrete use case quote ('what risk signals appeared this week') and two explicit exclusions with the alternative to use instead (company_history for per-company, /v1/signals for the full feed). This is exactly the when/when-not/alternative structure that removes ambiguity.

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.