Skip to main content
Glama
Sign In

ZeroClickz

by com.zeroclickz
OverviewDiscussionsAdmin

Prove a receipt is in the public log

receipt_proof
Read-onlyIdempotent

Get the inclusion proof for a signed receipt: its position in the public add-only receipt log, the audit path and the signed tree head. Recompute the root to check nothing was changed or hidden.

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": {
      "receipt_id": "<receipt_id>"
    },
    "name": "receipt_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoOptional API key (zck_...), session token or guest requester_token for this call only. Overrides the connection's Authorization header. Use it to follow up on a request you posted as a guest.
receipt_idYesReceipt id, e.g. rcpt_abc123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds meaningful context by calling the log public and add-only, which tells the agent entries are append-stable, and by stating the verification procedure the caller should follow. It does not say how it behaves for an unknown or not-yet-anchored receipt id.

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?

Two tight sentences: the first delivers the resource and its returned components, the second delivers the reason to call it. Nothing is redundant and the key noun phrase is front-loaded.

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 correctly takes on the burden of describing the return payload (position, audit path, signed tree head) and how to use it. Only the failure modes for missing receipts are left unstated, which is a minor gap for a two-parameter read tool.

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 parameters are already documented, including the token override semantics. The description only restates the receipt concept and adds no format, validation or ID-resolution detail beyond the schema, so the baseline of 3 applies.

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?

It names a specific verb and resource (get the inclusion proof for a signed receipt) and spells out what the proof contains: log position, audit path and signed tree head. No sibling tool in the list covers receipt logs, so the tool is unambiguous even though no sibling is named for contrast.

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?

The second sentence supplies the actual use case — recompute the root to confirm nothing was changed or hidden — which is clear invocation context. It stops short of explicit when-not conditions or pointing to an alternative (e.g. what to do if the receipt is not yet in the log).

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

All ZeroClickz 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