Skip to main content
Glama
Sign In

RelayLink

by ai.relaylink
OverviewDiscussionsAdmin

Check inbox

check_inbox
Read-onlyIdempotent

List new package envelopes for the user — the quick-read layer: sender, the ask (its shape and urgency, and the question when there is one), the TL;DR, the start of their note (labeled with its provenance — verbatim only when marked so, otherwise AI-drafted and sender-approved), whether a fuller message is attached, and the thread. Cheap call — use it whenever the user asks about messages, a contact by name, or at the natural start of a work session. The message and the deeper context are NOT included: fetch a package with get_package when the user's question already calls for its content — what somebody said, what they meant — rather than reading every envelope aloud.

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

Input Schema

NameRequiredDescriptionDefault
tagNoNarrow to threads the user has tagged with this word. Omit for everything.
limitNoEnvelopes per page (default 20, max 50).
offsetNoSkip this many envelopes, most recent first (default 0). The reply says the offset of the next page.
includeReadNoInclude already-read packages (default false: unread only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds material context they do not carry: this is a 'cheap call', the message body and deeper context are explicitly NOT returned, and note text is provenance-labeled (verbatim only when marked, otherwise AI-drafted and sender-approved). That provenance caveat is behaviorally significant for how the agent should present 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?

Front-loaded with the verb and resource, then the payload enumeration, then usage routing — a sensible order with no filler sentences. The middle sentence is very dense with stacked parentheticals about urgency and provenance, which costs some readability but every clause carries information.

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?

No output schema exists, and the description compensates by describing the returned fields in detail, including what is deliberately omitted (message body, deeper context) and how to get it. For a 4-parameter, optional-only read tool, nothing an agent needs to call 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?

Schema description coverage is 100%, so tag, limit, offset, and includeRead are fully documented in the schema itself. The description adds only the implicit notion of 'new' (unread) envelopes and says nothing about tag filtering or paging, so it neither compensates for nor detracts from the schema. Baseline 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 new package envelopes for the user') and then enumerates exactly what each envelope contains: sender, the ask with shape/urgency, TL;DR, note start with provenance, attachment flag, thread. It explicitly marks itself as 'the quick-read layer' and contrasts with get_package, so an agent can separate it from siblings 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?

Gives concrete positive triggers ('whenever the user asks about messages, a contact by name, or at the natural start of a work session') and an explicit exclusion plus named alternative: fetch a package with get_package when the question already calls for its content, rather than reading every envelope aloud. Both when-to-use and when-not-to-use are stated.

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