Dove

List my requests

list_requests

Read-onlyIdempotent

Lists send and access requests newest first, optionally filtered by status, so you can check whether an operator approved request_send or request_access.

Instructions

List the send and access requests this connection made, newest first; status filters them. Use it to see whether the operator approved a request_send or request_access. Each request has its status (pending, approved, denied, cancelled, expired, done) and, per item, its state (pending, scheduled, sending, sent, skipped, failed, missed, send_unknown, cancelled, denied) and reason code. send_unknown means the send may have happened: never retry it, check Sent. Access requests list each asked grant (pending, granted, active, ended, not_approved) and when temporary rights end.

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

Input Schema

Name	Required	Description	Default
`status`	No	Only requests with this status.

Output Schema

Name	Required	Description	Default
`requests`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026
- addedInput schema / properties / status / description
```
Added value: +"Only requests with this status."
```
First observedv0.11.0Nov 14, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare this as a safe, idempotent, closed-world read; the description goes well beyond that with result ordering (newest first) and a real operational hazard: send_unknown means the send may have occurred, never retry it, check Sent. It also explains that access requests expose per-grant state and temporary-rights expiry, which an agent cannot infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead clause is well front-loaded and the send_unknown warning earns its place, but the long parenthetical enumerations of request statuses, item states, and grant states duplicate what the input enum and the output schema already provide. Roughly a third of the text could be cut without losing decision-relevant information.

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 single-optional-parameter read tool with full annotations and an output schema, the description covers what matters: what is listed, how it is ordered, how to filter, and how to interpret the risky send_unknown state. Nothing essential is missing, though the grant-state list is redundant with the output schema.

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 the single status parameter already carries an enum with descriptions, so the description adds little. "status filters them" plus a restatement of the enum values largely duplicates the schema rather than explaining semantics such as whether filtering excludes in-flight requests.

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 ("List the send and access requests this connection made"), plus scope (this connection), ordering (newest first), and the filtering dimension. It also ties the resource to the originating siblings request_send and request_access, so an agent can tell what it is looking at without opening a 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 an explicit use case: "Use it to see whether the operator approved a request_send or request_access." That is a clear when-to-use signal that routes the agent away from the request-creating siblings. It stops short of naming a when-not condition or pointing at cancel_request for the opposite operation.

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