Skip to main content
Glama

issuer_filings

Retrieve Spanish CNMV filings for a specific company, newest first, by NIF or company name; filter by date range or filing kind to review announcements and history.

Instructions

Filings from one specific company at the Spanish CNMV, newest first.

issuer: its Spanish tax id / NIF ("A64907306") is best: the CNMV filters by it directly, so even years of history come back in seconds. A company name or part of it ("Cellnex", "telefonica") also works but scans every filing, so keep days small (7-14) when searching by name. since / until: optional date range (YYYY-MM-DD) for history; overrides days. Price-sensitive announcements (IP) exist from Feb 2020 onwards.

complete is false if the search was cut short; found counts every match, returned how many are in filings.

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": {
      "issuer": "<issuer>"
    },
    "name": "issuer_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
kindNoall
limitNoMax filings returned, newest first.
sinceNo
untilNo
issuerYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.3
    • addedInput schema / properties / days / maximum
      Added value: +366
    • addedInput schema / properties / days / minimum
      Added value: +1
    • addedInput schema / properties / limit / description
      Added value: +"Max filings returned, newest first."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
      -  "result": {
      -    "items": {
      -      "additionalProperties": true,
      -      "type": "object"
      -    },
      -    "title": "Result",
      -    "type": "array"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
    • changedOutput schema / title
      Previous value: -"issuer_filingsOutput"New value: +"issuer_filingsDictOutput"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses performance characteristics (NIF lookups are fast even over years, name lookups scan everything), data coverage limits (price-sensitive announcements only from Feb 2020), and result-completeness semantics (`complete` false when truncated, `found` vs `returned`). It omits error behavior and rate limits, but the core operational profile is disclosed.

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 first sentence front-loads the purpose, then each paragraph handles one parameter concern with no filler; the `issuer` advice is the longest because it carries the most risk. Minor cost from backtick formatting and an abbreviation (IP) introduced without expansion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the description still usefully explains the `complete`/`found`/`returned` fields, and it covers the two highest-risk parameters in depth. The undefined `kind` enum values and undocumented `limit` keep it from being fully complete for a 6-parameter tool.

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 only 17%, so the description has to compensate and does so for `issuer`, `days`, `since`, and `until`. However `kind` is never explained — the enum values IP and OIR are used without defining OIR — and `limit` is left entirely to the schema. Meaningful but partial coverage of a 6-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'Filings from one specific company at the Spanish CNMV, newest first.' An agent can immediately tell this is a per-issuer filing lookup with newest-first ordering. It does not explicitly contrast with the sibling latest_filings, but 'one specific company' vs. what is presumably a market-wide feed is clear enough.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Strong practical routing advice: use the NIF because the CNMV filters by it directly, use a name only with a small `days` window (7-14), and use since/until for history since they override `days`. The one gap is it never names when to prefer latest_filings instead.

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

Deploy Server

Other Tools