Skip to main content
Glama

List My Confirmation Receipts

list_my_confirmation_receipts
Read-onlyIdempotent

List the confirmation receipts you granted in X1 that have not been used yet, on this connection's surface. Use it after someone approves a batch of queued proposals in X1 so you can act on exactly what they approved. Seeing a receipt grants nothing on its own: X1 re-verifies the signature, the surface, the tool, your live entitlements, and the exact arguments before anything runs, so a receipt can only ever perform the one action that was approved, once. Quoting it again either returns that same result or is refused; it never runs the action a second time.

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_my_confirmation_receipts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pending receipts to return. Defaults to 20.
toolNameNoOnly receipts approving this exact tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only, non-destructive, and idempotent annotations, it explains that merely seeing a receipt grants nothing and details the downstream signature, surface, tool, entitlement, and argument verification. The one-action-once guarantee and replay behavior—same result or refusal, never a second execution—provide especially useful lifecycle and safety context.

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?

The purpose and post-approval use case are front-loaded, and the remaining sentences contain relevant security and replay information. However, the final two sentences are dense and devote considerable space to downstream receipt execution for a simple two-parameter listing tool.

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 tool with two optional filters, the description covers result scope, timing, security implications, and receipt reuse well enough to support correct selection and invocation. With no output schema, it would be more complete if it briefly identified what a returned receipt contains or how the agent should use it next; ordering and empty-result behavior are also unspecified.

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%, and both `limit` and `toolName` already have clear descriptions, including the default and exact-match filtering behavior. The description adds no parameter-specific syntax, interactions, or examples, so the fully documented schema appropriately establishes the baseline score.

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?

The opening sentence gives a specific verb, resource, and scope: unused confirmation receipts granted in X1 on the current connection's surface. It does not explicitly distinguish these receipts from nearby sibling concepts such as action requests or approved artifacts.

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 an explicit use case: call this after someone approves a batch of queued proposals so the agent can act on exactly what was approved. There is no when-not guidance or named alternative for other approval-related queries.

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.