Skip to main content
Glama

One of the person’s letters

get_my_letter
Read-onlyIdempotent

READ ONLY. The current status of one of the person’s own letters by its Piloxa reference, once this chat is connected: printer acceptance, USPS acceptance, delivery or return, the return receipt, each with its source and when it was last checked, the reply-by date if the letter set one, and where to download the mailing record (signed in on piloxa.com). A missing USPS scan means unknown, not failed; delivered does not mean read; a passed reply-by date does not mean nobody answered. Ask the person whether a reply arrived before suggesting a follow-up.

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": {
      "reference": "<reference>"
    },
    "name": "get_my_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesThe Piloxa reference (act...) from list_my_letters.

Output Schema

NameRequiredDescriptionDefault
letterNo
connectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value on top: an auth/connection prerequisite, where to download the mailing record, and crucial interpretation rules (missing scan means unknown, delivered is not read, passed reply-by date is not a non-answer). The only redundancy is the leading 'READ ONLY', which restates 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-loads the key constraint, then packs the return facets and caveats efficiently into one dense but scannable sentence. The interpretive sentence earns its place; only the 'READ ONLY' prefix is wasted against the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read with an output schema and full annotation coverage, the description closes the remaining gaps: connection prerequisite, download destination, and how to correctly interpret ambiguous status fields before acting. Nothing an agent needs to call and use it correctly is missing.

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?

Single parameter with 100% schema description coverage, so the schema already explains the Piloxa reference format and its origin in list_my_letters. The description repeats the reference concept but adds no syntax or format detail beyond the schema; 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 read of a single resource — 'the current status of one of the person's own letters by its Piloxa reference' — and enumerates the facets returned (printer acceptance, USPS acceptance, delivery/return, return receipt). It is clearly distinct from the list tool, though it never explains how it differs from the sibling get_certified_letter_status, which sounds adjacent.

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?

Gives a prerequisite ('once this chat is connected') and downstream behavioral guidance ('ask the person whether a reply arrived before suggesting a follow-up'), which implies usage context. However, it never says when to prefer this over get_certified_letter_status or list_my_letters, so tool selection 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