Skip to main content
Glama

List disclosure events since a date

list_events_since
Read-onlyIdempotent

Dated disclosure events for an issuer since a date, each with its source address, served by the MCP of the issuer's home market.

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": {
      "identifier": "<identifier>"
    },
    "name": "list_events_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
cursorNo
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds useful routing context ('served by the MCP of the issuer's home market') and notes each event carries a source address, but says nothing about pagination behavior or result ordering beyond that.

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?

A single front-loaded sentence with no filler. Slightly awkward phrasing around 'served by the MCP of the issuer's home market,' but it is efficient and wastes no words.

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

Completeness2/5

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

With four undocumented parameters, no output schema, and a mutation-free but nontrivial retrieval contract, the description should explain identifier format, date format, and pagination semantics. It leaves half the call surface and the cursor behavior entirely to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, yet it only touches 'since' and the issuer identifier. The limit and cursor parameters are completely unexplained, and the expected format of identifier and since is never stated.

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?

The description names a specific resource (dated disclosure events), a scope (for an issuer), and a filter (since a date), which lets an agent distinguish it from get_record or get_signal. The listing verb is only implied by the tool name, but the retrieval purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus siblings like get_record or get_signal, nor any prerequisite or exclusion. The only implicit cue is the date filter, leaving the agent to infer selection criteria from names alone.

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.