Skip to main content
Glama

Connect this chat to the person’s Piloxa letters

connect_my_letters

Use when the person wants to see, track or follow up on letters they sent with Piloxa in ANOTHER conversation, or wants their saved return address used. Returns a link and a 4-character code. Give the person both: they open the link, sign in with their email on piloxa.com, check the code matches, and press Allow. Only then can list_my_letters, get_my_letter and create_followup_draft see their letters, and only in this chat. It reads nothing, mails nothing and charges nothing. The person can disconnect at any time on that page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
connectedYes
expires_atNo
match_codeNo
connect_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), it discloses the exact return shape (link plus 4-character code), the required human steps (open link, sign in with email on piloxa.com, verify code, press Allow), and that the agent must relay both values. It also bounds the side effects ('reads nothing, mails nothing, charges nothing') and states the user can disconnect at any time — reversibility that annotations do not convey.

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?

Selection guidance is front-loaded in the first sentence, followed by the return values and then the user-facing procedure. Every sentence carries load, though the instruction sequence is fairly dense and slightly long for a single tool definition.

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 zero-parameter authorization-handshake tool, the description covers trigger, return values, the human-in-the-loop steps, scope limits (which tools gain access, in which chat), side-effect boundaries, and revocation. An output schema exists, yet the description's summary of the link and code still adds actionable relay instructions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing to disambiguate; the baseline for a zero-parameter schema applies. The description adds no parameter meaning, but none is needed.

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?

The description states a specific action (granting this chat access to Piloxa letters via a link-and-code authorization) and its trigger condition (letters sent in ANOTHER conversation, or needing the saved return address). It explicitly distinguishes itself from list_my_letters, get_my_letter and create_followup_draft, which cannot see the letters until this runs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is pinned to a concrete situation ('letters they sent with Piloxa in ANOTHER conversation'), and the description names the three sibling tools that depend on it, so the agent knows both when to call it and what it unlocks. The per-chat scoping ('only in this chat') implicitly tells the agent not to re-run it for the current chat's already-authorized letters.

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