Skip to main content
Glama
Sign In

RelayLink

by ai.relaylink
OverviewDiscussionsAdmin

Mail forwarded in

list_forwarded
Read-onlyIdempotent

List email the user has forwarded into RelayLink from elsewhere — their own copy of messages from outside, kept so you can read them. Subjects and senders only; read_forwarded returns one in full. This is NOT correspondence between RelayLink accounts: nobody else can see it, nothing was sent to anybody, and the sender shown is whatever the message claimed, which forwarding routinely rewrites.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many, up to 50. Omit for 20.
offsetNoWhere to start. Omit for the newest.
includeArchivedNoInclude ones already archived. Omit for the ones still in play.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, but the description adds real context beyond them: the folder is private, nothing was sent, and the displayed sender is untrustworthy because forwarding rewrites it. That provenance caveat is genuinely useful. It stops short of describing ordering or any limits on volume.

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 core definition, then the read_forwarded pointer, then the exclusion. Dense and nearly waste-free, though the negative-framing clause is long and could be tightened by a sentence without losing meaning.

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?

Three optional parameters, no output schema, and the description compensates by stating what comes back ('Subjects and senders only'), which an agent needs. Nothing about pagination defaults is needed since the schema supplies them; only ordering/volume expectations are left implicit.

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 description coverage is 100% and each parameter is documented in the schema itself (limit, offset, includeArchived). The description adds no syntax or default behavior beyond the schema, so the baseline of 3 applies.

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 forwarded-in email), defines its scope precisely (the user's own imported copies), and contrasts it with read_forwarded for full content. An agent can distinguish it from search_messages and thread tools without opening the schema.

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?

Explicitly routes to read_forwarded for full messages and draws a hard exclusion line — 'This is NOT correspondence between RelayLink accounts' — which is exactly the misclassification an agent would otherwise make. When-to-use (index browsing) and when-not-to-use are both present.

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

All RelayLink toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources