Skip to main content
Glama

middleware_list_transactions

Read-only

Middleware admin only: list persisted middleware transactions for the selected middleware account, optionally filtered by domain. Pass nextCursor as cursor for the next page.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo0
domainNo
account_idNo
customer_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / customer_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Customer Id"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the admin-only access restriction, the fact that transactions are 'persisted', and the nextCursor-to-cursor pagination loop, which is useful context beyond annotations but doesn't cover ordering or result size behavior.

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?

Two sentences, front-loaded with the access restriction and the core action; the pagination hint is placed last where it belongs. No filler, though 'Pass nextCursor as cursor' is slightly awkward phrasing for what the cursor parameter accepts.

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

Completeness3/5

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

The auth requirement, scope, filter, and pagination are covered, and an output schema exists to carry return values. Gaps remain for a five-parameter tool at 0% schema coverage: limit semantics (default 100, max?) and customer_id are never explained.

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 0%, so all five parameters rely on the description. It explains domain filtering, the cursor/nextCursor mapping, and hints at the account scope, but limit, customer_id, and the exact role of account_id remain undocumented in both places.

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 and resource ('list persisted middleware transactions') plus scope ('for the selected middleware account') and an optional filter ('by domain'). An agent can distinguish this from middleware_get_transaction, which fetches one transaction, though the description never names that sibling explicitly.

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?

'Middleware admin only' establishes a clear prerequisite, and the domain filter plus cursor instruction imply when pagination applies. It stops short of contrasting with middleware_get_transaction or stating what happens when the account is omitted.

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.