Skip to main content
Glama

Get monitoring events

get_monitoring_events
Read-only

Returns the authenticated user's monitoring events: material reputation changes detected on their monitored addresses, oldest first, each with the change type, a summary, and the band transition. Also returns a deterministic digest that rolls up the window into one sentence. Page forward by passing the returned nextCursor as cursor. Bound the window with since and until, or restrict to one address with address. Costs zero credits.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of events (1-100, default 20)
sinceNoISO-8601 lower bound. Only events at or after this time are returned.
untilNoISO-8601 upper bound. Only events at or before this time are returned.
cursorNoPass the nextCursor from a prior call to page forward.
addressNoRestrict to one monitored address (0x...). Omit for the whole portfolio.

Output Schema

NameRequiredDescriptionDefault
digestYesDeterministic rollup of the events in this window
eventsYesMonitoring events in the window, oldest first
hasMoreYesTrue when more events remain past this page
nextCursorYesCursor for the next page, or null when none remain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds real context beyond that: deterministic oldest-first ordering, a deterministic digest, cursor-based pagination mechanics, and the fact that calls cost zero credits. It omits default page size behavior at the description level, but the schema covers that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what is returned, then paging, then filtering, then cost — a natural call-order for the agent. Four compact sentences with no filler and nothing repeated from the title.

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, so return-shape detail is not required, and the description still conveys ordering and digest presence. Combined with annotations covering the safety profile and a fully documented schema, an agent has everything needed to call this correctly on the first try.

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 coverage is 100%, so all five parameters are already documented, and the description mostly restates them (cursor paging, since/until bounds, address scoping) rather than adding format or edge-case semantics. The 'omit for the whole portfolio' guidance mirrors the schema, so this lands at the baseline.

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 ("Returns the authenticated user's monitoring events") and pins down the payload: reputation changes on monitored addresses, oldest first, with change type, summary, band transition, plus a roll-up digest. This is clearly distinguishable from the history/narrative siblings, which cover screening rather than monitored-address events.

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?

Gives concrete operational guidance: page forward with nextCursor as cursor, bound the window with since/until, or narrow to a single address with address. It stops short of explicitly saying when to prefer this over get_address_screening_history or get_screening_history, so the sibling routing is left implicit.

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.

Resources