Skip to main content
Glama

List the person’s letters

list_my_letters
Read-onlyIdempotent

READ ONLY. The person’s own recent Piloxa letters, from any conversation, once this chat is connected with connect_my_letters. Optional query matches the recipient’s name or company, or the start of a Piloxa reference. Returns reference, recipient name, service, status, dates and where the status came from; never the letter text or full addresses. Without a connection it returns how to connect and nothing else.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoOptional: a recipient name or company, or the start of a reference.

Output Schema

NameRequiredDescriptionDefault
foundNo
lettersNo
connectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered elsewhere. Beyond that, the description adds real value by bounding the payload ('never the letter text or full addresses') and enumerating returned fields, plus the disconnected-state behavior; the 'READ ONLY' opener itself is redundant with readOnlyHint.

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?

Front-loaded with the operation and scope, then connecting requirement, query semantics, and return payload in a tight sequence with no filler. The uppercase 'READ ONLY' lead-in duplicates an annotation and is the one sentence that does not earn its place.

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, yet the description still outlines the shape of the result and its exclusions, and it covers the connection prerequisite failure mode. The remaining gap is the undocumented 'limit' parameter, which for a bounded list tool leaves default page size and truncation behavior unclear.

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 only 50%, and only 'query' is described in the schema; the description usefully expands it to 'recipient's name or company, or the start of a reference', which is meaningfully richer. The 'limit' parameter is documented in neither place, and no defaults or paging behavior are mentioned, so half the surface remains unaddressed.

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?

Names a specific resource ('the person's own recent Piloxa letters, from any conversation') and scope, and implicitly contrasts with the connected/failure path. The verb is carried by the name/title rather than restated in the first clause, but an agent can still tell it is a listing operation over all letters.

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?

Explicitly states the prerequisite ('once this chat is connected with connect_my_letters') and the exact fallback behavior when unconnected ('returns how to connect and nothing else'). It also gives the query's intended matching semantics, though it does not say when to prefer this over looking up a single letter.

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