Skip to main content
Glama

Coline

List events

alert_events_list
Read-onlyIdempotent

Events tools sent, quiet ones included: 'what deployed today?'. Filter by sender, address, card, time or words.

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": {
      "workspace": "<workspace>"
    },
    "name": "alert_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sinceNo
cardIdNo
senderIdNo
addressIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description's one contribution is 'quiet ones included', which tells the agent results include suppressed/silent events rather than only active ones -- a real behavioral detail. It says nothing about default/max page size (limit 50/200) or result ordering, which matter for a list tool.

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?

A single compact sentence plus a parenthetical example -- no filler, and the distinguishing scope detail (quiet events included) comes before the filter list.

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?

With 7 parameters, an output schema and rich annotations, most structured burden is carried elsewhere. Still missing is any note on pagination/limit behavior and on how this differs from the near-identically named list_events and search_events siblings.

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 only 14% (only 'workspace' is documented), so the description must compensate, and it largely does: 'sender, address, card, time or words' maps onto senderId, addressId, cardId, since and query. It does not explain the limit parameter or clarify that 'words' means free-text matching in query.

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

Purpose3/5

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

The phrase 'Events tools sent, quiet ones included' identifies the resource and a scope nuance (quiet events are returned), but the wording is garbled and never states a clear verb. Siblings list_events and search_events exist, and the description does nothing to distinguish this tool from them, so an agent cannot confidently pick it out of the catalog.

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?

The example question 'what deployed today?' implies a usage scenario and hints at a time-based query, which is a genuine, if indirect, usage cue. However there is no explicit when-to-use/when-not guidance and no reference to the alternatives (search_events, list_events), leaving routing to inference.

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