Skip to main content
Glama

Lister la capture

dandori_inbox_list
Read-onlyIdempotent

Lister les éléments de Capture (boîte de réception) : à trier par défaut

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

Input Schema

NameRequiredDescriptionDefault
stateNopending : à trier (défaut) ; deferred : gardés pour plus tard ; all : les deux

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the default filter state (pending/à trier), and says nothing about ordering, volume, or pagination of results.

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?

A single short sentence, front-loaded with the verb and resource, with the default scope appended. Nothing is wasted, though the phrasing is so terse that it borders on under-specification for an agent unfamiliar with the domain.

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 zero-required-parameter, read-only list tool with full schema coverage and no output schema, the description covers what is listed and the default scope. Missing only return-shape or pagination hints, which is a minor gap given the annotations already convey the safe read profile.

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 enum parameter already documents pending/deferred/all with their meanings. The description merely echoes the default ("à trier par défaut") rather than adding syntax or behavioral nuance, so baseline 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?

States a specific verb and resource: "Lister les éléments de Capture (boîte de réception)", with the parenthetical clarifying that Capture means inbox. It implicitly contrasts with the mutation/convert siblings (dandori_inbox_convert, dandori_quick_capture) by being purely a listing, but never names an alternative 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?

The phrase "à trier par défaut" signals the default scope but gives no explicit when-to-use/when-not-to-use guidance relative to dandori_inbox_convert or dandori_quick_capture. An agent can infer this is the read path for the inbox, but the routing is left to inference.

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.

Resources