Skip to main content
Glama
LinkedParticles

Particles

Official
by LinkedParticles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

events_list

List operator events newest first, filtered by particle, subject, corpus entry, or event type. Use it to audit what changed and when for a specific record.

Instructions

List operator events, newest first, optionally filtered.

Args:
    particle: Only events touching this particle id.
    subject: Only events touching this subject id.
    corpus_entry: Only events touching this corpus entry id.
        (At most one of ``particle`` / ``subject`` / ``corpus_entry``.)
    event_type: Only events of this type, e.g. ``SOURCE_RETRACTED``,
        ``SUBJECTS_SPLIT``, ``TRUST_CHANGED``, ``REVIEW_RESOLVED``.
    limit: Maximum events to return (default 50).

Input Schema

NameRequiredDescriptionDefault
limitNo
subjectNo
particleNo
event_typeNo
corpus_entryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.210.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavior burden. It usefully discloses ordering (newest first), the default limit of 50, and the mutual-exclusivity constraint on the three filter ids, but says nothing about whether limit is capped, how to page past 50 results, or what happens with zero matches.

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 one-line summary followed by a compact Args block; every line carries information. The docstring formatting is slightly heavy for a tool description but there is no filler or repetition.

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

Completeness3/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 values need not be explained, and all five parameters are documented. What is missing is paging behavior: with a limit default of 50 and no offset/cursor documented, an agent cannot tell how to retrieve further events, nor whether events feed into event_show by id.

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 description coverage is 0%, so the description must compensate and mostly does: it defines all five parameters, explains the 'touching this id' semantics of the three filter ids, and gives concrete event_type examples (SOURCE_RETRACTED, SUBJECTS_SPLIT, TRUST_CHANGED, REVIEW_RESOLVED). It stops short of saying what form the ids take or listing the complete set of event types.

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 verb and resource ('List operator events') plus ordering ('newest first') and filtering scope. It does not differentiate itself from siblings like event_show or the other *_list tools, but the verb+resource pairing is unambiguous about what it returns.

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

Usage Guidelines3/5

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

Usage is only implied: the reader infers this is the enumeration tool versus event_show for a single event. The one genuinely useful routing rule is the parenthetical that at most one of particle/subject/corpus_entry may be supplied, but there is no explicit 'use this when' or named alternative.

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