Skip to main content
Glama

latest_filings

Retrieve Spanish CNMV filings from the past 1–14 days, filtered by price-sensitive or other regulatory announcement type and sorted by publication time.

Instructions

Latest filings published at the Spanish CNMV, newest first.

kind: "IP" = price-sensitive announcements, "OIR" = other regulatory announcements. For one company, or for longer periods, use issuer_filings.

complete is false if the search was cut short; found counts every match, returned how many are in filings. In each filing, issuer is the company the filing is about: a bidder's announcements about a takeover, for example, are filed under the target.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLast N days (1-14).
kindNoall
limitNoMax filings returned, newest first.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.3
    • addedInput schema / properties / days / description
      Added value: +"Last N days (1-14)."
    • addedInput schema / properties / days / maximum
      Added value: +14
    • addedInput schema / properties / days / minimum
      Added value: +1
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "description": "Max filings returned, newest first.",
      +  "maximum": 200,
      +  "minimum": 1,
      +  "title": "Limit",
      +  "type": "integer"
      +}
    • 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: -"latest_filingsOutput"New value: +"latest_filingsDictOutput"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does it well: it discloses result ordering, truncation signaling via `complete`, the `found` vs `returned` distinction, and the non-obvious issuer-attribution rule where bidder announcements for a takeover appear under the target. It does not mention authentication, rate limits, or whether results are cached/live.

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?

Three short, front-loaded paragraphs: purpose, filter semantics, then output/caveat notes. No wasted clauses, though the `found`/`returned`/`complete` explanation partially restates what the output schema already declares.

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?

An output schema exists and carries the return structure, so the description needn't restate field definitions; what it does add — truncation semantics and issuer attribution — is exactly the non-obvious part. With all three parameters documented across schema and description and the sibling routing spelled out, nothing needed for correct invocation 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 67%, and the description compensates for the gap by explaining what `kind` values actually mean ("IP" = price-sensitive, "OIR" = other regulatory), which goes beyond the bare enum labels. It also reinforces the newest-first semantics tied to `limit`, though `days` gets no elaboration beyond the schema's own 1-14 range note.

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 the exact resource (filings at the Spanish CNMV), the ordering (newest first), and the scope (latest), which is specific enough to be actionable. It also directly separates itself from the sibling by stating that per-company or longer-period queries belong to `issuer_filings`.

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?

The definition names the alternative tool explicitly and gives the conditions that select it: one company, or longer periods. Combined with the `kind` semantics (IP vs OIR vs all), an agent has both routing guidance and filtering guidance without inference.

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