Skip to main content
Glama

payments_events

Read-onlyIdempotent

Paginated feed of Stripe webhook events the platform received for this project (from the payments_events ledger). It can drive an in-product activity feed or confirm webhook reception during integration. The webhook handler is idempotent — duplicate Stripe redeliveries appear once.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOptional Stripe event type filter, e.g. `checkout.session.completed`.
limitNoPage size (1-200). Default 50.
beforeNoCursor — the previous page's `next_cursor` (ms epoch).
project_idNoOptional project UUID/subdomain filter. Omitted: every event attributed to this developer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and idempotent, so the safety profile is covered. The description adds genuinely useful non-obvious behavior: pagination, the backing ledger, and that duplicate Stripe redeliveries are collapsed to a single row, which prevents an agent from trying to de-duplicate or misreading counts.

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?

Three sentences, front-loaded with the resource definition, followed by use cases and then the dedup caveat. No filler; the parenthetical ledger reference and the idempotency note both add information an agent needs.

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?

For a read-only, four-parameter, no-output-schema listing tool, this covers source, pagination, dedup semantics and consumer contexts adequately. It could still state ordering (newest-first) and what a page boundary looks like, but nothing essential to calling it correctly is missing.

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% with each of the four parameters individually described (type filter, page size, cursor, project filter), so the baseline is 3. The description only echoes pagination and does not clarify cursor semantics, default ordering, or page-size implications beyond what the schema states.

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 resource and shape: a paginated feed of Stripe webhook events received for this project, sourced from the payments_events ledger. An agent can distinguish it from sibling read tools like payments_transactions because it is explicitly framed as received-webhook records, though no sibling is named as a contrast.

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?

Offers two concrete consumption contexts (in-product activity feed, confirming webhook reception during integration), which gives real usage signal. It does not say when to prefer payments_transactions or payments_checkout instead, so the routing decision is left inferred from the purpose sentence.

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