RelayLink

Projects the user is on

project_list

Read-onlyIdempotent

List the RelayLink projects the user owns or has joined, each with its state, their role, how much is open or blocked, and the next thing due. Pending invitations the user has not answered are listed last, with a note that accepting or declining happens in the browser. project_open reads one project in full. Reads only. This is shared with everybody on the project: every member can read it, so use these tools only for work the user means to be visible to the people they have put on this project. A private note, task or preference that is only the user's own is the notebook's (notebook_*) instead, and a bare "add a task" may be meant for another connected app — if more than one destination is plausible and the user has not said which, ask once and stay with the answer.

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

Input Schema

Name	Required	Description
`role`	No	owned \| joined \| all. Defaults to all.
`state`	No	active \| on_hold \| completed \| cancelled \| all. Defaults to every project still active or on hold.
`includeArchived`	No	true to include archived projects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: every member of a project can read this, pending invitations appear last and must be accepted or declined in the browser rather than through this tool. It does not mention result size, ordering beyond invitations, or truncation, which keeps it from a 5.

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?

Purpose and payload are front-loaded, with alternatives and caveats after. Most sentences earn their place, but the trailing 'bare add a task' paragraph concerns destination choice for creation rather than listing, so it is slightly beyond this tool's remit.

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?

For a no-output-schema, zero-required-parameter list tool this covers what comes back, how invitations are handled, and where to go instead. What remains unstated — pagination, total counts, sort order — is minor but not nothing given the absence of an output schema.

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 coverage is 100% and each of role, state, and includeArchived carries its allowed values and defaults inline, including the non-obvious default of 'every project still active or on hold'. The description adds no filtering syntax or semantics beyond that, so the 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?

A specific verb (List) plus resource (RelayLink projects the user owns or has joined) plus an enumeration of what each row carries: state, role, open/blocked counts, next due item. It explicitly distinguishes itself from the sibling project_open, so an agent can choose between them without opening either 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?

It gives explicit routing: project_open for one project in full, notebook_* for anything private to the user, and 'ask once' when a bare 'add a task' could target another connected app. It also states a when-not condition (do not use for work the user does not intend to be visible to project members).

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?