Meridian

List Events

events_list

Read-only

Lists an app's Plan Builder metered-usage event catalog: event_id, handle, key (pass this as eventKey to the @the-meridian/sdk track({ eventKey: "<key>" }) call), name, unit, description, the default metering terms (default_included_quantity, default_overage_rate, default_overage_unit, default_capped_amount), and the per-plan terms that override those defaults. Takes the app_id returned by apps_list.

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": {
      "app_id": "<app_id>"
    },
    "name": "events_list"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes	The app uuid returned by `apps_list`.
`organization_id`	No	An organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=false, so safety is covered; the description adds substantive scope detail beyond that — the exact returned field set, including default metering terms and the per-plan overrides layered on top of them. It does not mention pagination, ordering, or whether the list is exhaustive, which keeps it out of the top band.

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?

Purpose is front-loaded in the first clause, followed by a dense but useful field enumeration rather than filler. The long parenthetical listing of default metering fields is heavy but is the only place the return shape is documented, so it earns most of its length.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so thoroughly by naming every field returned. The remaining gaps — list size, ordering, and pagination — are mild for a small per-app catalog, but they are unstated.

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 `app_id` and `organization_id` (including slug resolution) are already fully documented in the schema. The description's only parameter-related statement repeats the `app_id` provenance from `apps_list` and never touches `organization_id`, so it adds little meaning beyond structured fields — baseline 3.

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 description opens with a specific verb and scoped resource ('Lists an app's Plan Builder metered-usage event catalog') and then enumerates exactly what a record contains, including the `key` field and its downstream use. An agent can distinguish this from `events_create` or `apps_list` without opening any schema.

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?

It gives a concrete prerequisite chain ('Takes the `app_id` returned by `apps_list`') and an implicit workflow ('pass this as `eventKey` to the track call'), which tells the agent when this tool is needed. It stops short of naming an alternative or a when-not condition, so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meridian tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?