Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

List credit transactions

list_credit_transactions
Read-only

Lists the workspace's credit ledger, newest first: every grant, spend, reservation and refund with the balance after each entry. Filter by movement kind, reason or a time window. Use it to see where credits went, or to check for a stripe_topup entry after a credit purchase whose outcome was unconfirmed. An entry with free set to true was written while the workspace's credits were free: its amount is what the action would have cost, and no credits moved.

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

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by movement type
pageNoPage number, starting at 1
limitNoPage size (default 50, max 200)
sinceNoOnly entries at or after this time (RFC3339 or YYYY-MM-DD)
untilNoOnly entries at or before this time (RFC3339 or YYYY-MM-DD; a bare date means midnight UTC at the start of that day)
reasonNoFilter by what the credits were spent on or granted for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: chronological ordering, per-entry running balance, and the non-obvious rule that free=true entries record would-be cost with no credits actually moving. It does not discuss pagination behavior or result size, keeping it below 5.

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?

Front-loads what the tool returns, then the available filters, then the two use cases, then the free-entry caveat in a logical progression. The final sentence is long but carries non-obvious semantics that justify its length; there is little filler.

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 must convey the shape of results, and it does describe entries carrying a balance and a free flag. It stops short of enumerating other entry fields or explaining pagination semantics, so an agent still has some unknowns about the response, but nothing blocking correct invocation.

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 description coverage is 100%, with enum values and RFC3339/date format hints documented inline, so the schema does the heavy lifting. The description only restates the filter axes (movement kind, reason, time window) without adding syntax or edge-case behavior, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Lists the workspace's credit ledger'), plus ordering ('newest first') and content ('every grant, spend, reservation and refund with the balance after each entry'). An agent can tell this apart from a balance lookup or run-listing sibling without opening the 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?

Gives concrete use cases: seeing where credits went, and specifically checking for a stripe_topup entry after an unconfirmed credit purchase, which is a useful diagnostic path. It stops short of naming an alternative tool such as get_credit_balance or stating exclusions, so it is not a 5.

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

All Emailchaser toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources