ProofSnap

List captures

list_captures

Read-onlyIdempotent

Lists the captures of the connected ProofSnap account, newest first. Filters by page address, host, status, schedule and creation 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_captures"
  }
}

Input Schema

Name	Required	Description
`to`	No	Created before this ISO 8601 time.
`url`	No	Only captures of exactly this address.
`from`	No	Created at or after this ISO 8601 time.
`host`	No	Only captures of this host name, for example example.com.
`limit`	No	Default 20.
`cursor`	No	next_cursor of the previous page.
`status`	No
`schedule_id`	No

Output Schema

Name	Required	Description	Default
`captures`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful context that results are newest-first and scope is the connected account, but it does not discuss pagination behavior or limits beyond what the schema states.

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 with no filler. Scope and ordering are front-loaded, and the filter list follows efficiently.

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?

An output schema exists, annotations cover the safety profile, and the input schema documents most parameters, so the description needn't repeat return values. It is nearly complete for a filtered list tool, though it could mention pagination defaults or when to prefer a more targeted sibling.

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 75%, so the schema already documents most parameters, including the cursor and limit semantics. The description groups the filters as page address, host, status, schedule, and creation time, which adds a slightly higher-level map but does not explain syntax or behavior beyond the schema.

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 description gives a specific verb and resource ('Lists the captures'), scopes it to the connected ProofSnap account, and states the default ordering ('newest first'). It does not explicitly contrast with siblings like get_capture or list_matters, but the list-versus-get distinction is clear enough from the name and description.

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?

The description implies this is the tool for browsing or filtering captures by naming the available filter dimensions, but it never states when to use it instead of get_capture or compare_captures, nor does it mention prerequisites. Usage is inferable, not explicit.

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

All ProofSnap tools Inspect

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.