Skip to main content
Glama

Get charge timeline

charges_timeline
Read-only

Lists a charge's lifecycle events in order—created, transfers detected, confirmed, settled—so you can inspect status progression and diagnose where a payment stands.

Instructions

List the lifecycle events of one charge in order (created, transfers detected, confirmed, settled, ...).

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": {
      "id": "<id>"
    },
    "name": "charges_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA Klappay charge id (`ch_` followed by letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered externally. The description adds that events are returned in chronological order and hints at the event vocabulary, which is useful context. It omits whether the ordering is ascending or descending, whether results are paginated or truncated, and whether events from linked transfers are included — meaningful gaps for a timeline 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?

One sentence, front-loaded with verb and scope, with the event examples placed as a parenthetical tail. No filler or redundant restatement of the tool name.

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 one-parameter read tool with a fully documented schema and read-only annotations, the description covers purpose and shape well; no output schema means it needn't describe return fields. The unresolved details are minor but real: sort direction and whether the list is complete or truncated.

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?

There is a single required 'id' parameter and schema description coverage is 100%, so the schema already documents the ch_ prefix and pattern. The description's 'one charge' confirms the single-charge scope but adds no format or validation detail beyond the schema. Baseline 3 applies when the schema carries the parameter semantics.

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 (list) and resource (lifecycle events of one charge) and enumerates representative event types (created, transfers detected, confirmed, settled). An agent can tell this is a history/timeline read rather than a charge-detail fetch. It does not explicitly name charges_get as the alternative for current state, so sibling differentiation is only implicit.

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 implied by 'lifecycle events of one charge' — call it to see how a charge progressed. There is no explicit when-to-use/when-not guidance, no mention of when to prefer charges_get for current status, and no note about what to do if the charge has no events.

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