Meridian

Create Event

events_create

Adds a metered-usage event to an app's usage catalog. Requires name and key; key is what @the-meridian/sdk track({ eventKey: "<key>" }) reports against, must be lowercase letters, digits and underscores, is unique per app across both events and usage views, and cannot be changed afterwards. Optional unit, description, and default metering terms (default_included_quantity, default_overage_rate, default_overage_unit, default_capped_amount); omitted terms fall back to 0 / 0 / 1 / 0. Per-plan overrides are set in the Meridian dashboard. Call events_list first to avoid duplicating a key. Takes the app_id returned by apps_list. Returns the same shape as one events_list entry.

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": "<name>",
      "key": "<key>"
    },
    "name": "events_create"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	App-local key the SDK reports usage against: lowercase letters, digits, underscores. Unique per app across events and usage views. Immutable.
`name`	Yes	Display name for the event.
`unit`	No	Optional unit label, for example "call" or "order".
`app_id`	Yes	The app uuid returned by `apps_list`.
`description`	No	Optional free-text description.
`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.
`default_overage_rate`	No	Default per-unit overage price (min 0, default 0).
`default_overage_unit`	No	Default overage billing unit (min 1, default 1).
`default_capped_amount`	No	Default overage cap per period (min 0, default 0).
`default_included_quantity`	No	Default included quantity per period (min 0, default 0).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: `key` is immutable, unique per app across events and usage views, and constrained in format. It also explains omitted metering defaults fall back to 0 / 0 / 1 / 0 and that per-plan overrides are configured in the dashboard.

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?

The description is dense but front-loaded, starting with what the tool does and then covering required fields, constraints, defaults, and duplication checks. Every sentence carries actionable information for a create operation with immutable keys.

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?

For a 10-parameter create tool with no output schema, the description covers required fields, key immutability, default metering behavior, app resolution, duplicate avoidance, and return shape by reference to `events_list`. The remaining parameter details are fully covered by the schema.

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 coverage is 100%, so the schema already carries most parameter meaning. However, the description adds semantic context about how `key` maps to the SDK `track({ eventKey })` call and summarizes how omitted metering terms default together, which goes beyond individual schema fields.

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 states a specific verb and resource: it adds a metered-usage event to an app's usage catalog. It also clearly distinguishes the create operation from `events_list` by directing the agent to list first to avoid duplicate keys.

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 clear usage context by saying to call `events_list` first to avoid duplicating a key and that `app_id` comes from `apps_list`. It does not spell out every when-not condition, but the duplicate-key exclusion and prerequisite flow are strong 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?