RelayLink

List documents

attachment_list

Read-onlyIdempotent

List the user's documents: scope "owned" (saved or uploaded by this account), "received" (shared with this account by somebody else and not withdrawn), or "all". Optionally narrowed by query (a substring of the filename) or threadId (a conversation's received documents only). Reads only.

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

Input Schema

Name	Required	Description	Default
`limit`	No	At most this many, capped at 50.
`query`	No	A substring of the filename to filter by.
`scope`	No	owned \| received \| all. Defaults to owned.	owned
`offset`	No	How many to skip, for paging.
`threadId`	No	Limit received documents to one conversation, from get_thread or thread_status.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so "Reads only" is largely redundant. The description does add genuine behavioral detail about what "received" excludes (withdrawn shares), but it says nothing about pagination behavior, the result shape, or ordering beyond what schema defaults already show.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the resource and scope enumeration, followed by the narrowing options. Every clause carries information; nothing is padding.

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?

No output schema exists, yet the description doesn't say what a listed document contains or how paging results should be interpreted (though limit/offset are self-documenting). For a simple, zero-required-parameter list tool this is close to sufficient.

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?

Schema coverage is 100%, so baseline is 3, but the description adds cross-parameter meaning the schema lacks: threadId restricts *received* documents to one conversation, and query is a filename substring. This interaction guidance is real value beyond the field-level descriptions.

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?

Specific verb and resource ("List the user's documents") plus an enumeration of the three scope modes. It does not name sibling tools (e.g. attachment_read, search_messages) to differentiate, so it falls short of a 5, but the purpose is unambiguous.

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?

It clearly explains what each scope selects (owned = saved/uploaded by this account; received = shared by someone else and not withdrawn) and when to use the optional query/threadId narrowing. It stops short of naming an alternative tool or stating when *not* to call this one.

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

All RelayLink tools Inspect

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

Need Help?