Skip to main content
Glama
Sign In

RelayLink

by ai.relaylink
OverviewDiscussionsAdmin

List threads

list_threads
Read-onlyIdempotent

List the user's threads with participants, package count, state, and last activity (most recent 25).

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

Input Schema

NameRequiredDescriptionDefault
tagNoNarrow to threads the user has tagged with this word — the user's own private label, from list_tags. Omit for every thread.
groupNoNarrow to one group's threads, by name — an owned group or a Shared group the user is on, from list_groups. A Separate group's threads are found this way too, by its own auto-tag. Unrecognised narrows to nothing.
offsetNoSkip this many threads, most recent activity first (default 0). The reply says the offset of the next page.
projectNoNarrow to conversations filed under one notebook project, by name — the same projects notebook_find uses. Omit for every thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds ordering ('last activity') and the page cap of 25, but says nothing about what pagination does next or whether any thread types are excluded — leaving some behavioral gaps beyond the annotations.

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?

A single dense sentence with no filler, front-loading the verb and resource. It is perhaps too compact for its duty to distinguish siblings, but nothing is wasted.

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

Completeness3/5

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

With no output schema, the description shoulders return-value disclosure and does list the key fields and the 25-item limit. It omits the existence of filtering options and paging continuation, which an agent needs to use the tool fully.

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 the four filters (tag, group, project, offset) are fully documented there. The description names none of the filter dimensions, so it adds nothing 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?

Names a specific verb and resource ('List the user's threads') and adds the returned fields plus the 25-item cap, which the name alone does not convey. It does not distinguish the tool from siblings like get_thread, search_messages, or thread_ledger, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives (get_thread for a single thread, search_messages for searching, list_tags/list_groups for filtering sources). Only the implicit scope 'the user's threads' hints at usage; nothing excludes or routes.

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