Skip to main content
Glama
Sign In

RelayLink

by ai.relaylink
OverviewDiscussionsAdmin

Resume where the user left off

resume_handoff
Idempotent

Pick up work the user saved for themselves with save_handoff, from whichever assistant saved it: the most recent hand-off nothing has picked up yet, in full, marked as picked up. Call it when the user says "where were we", "pick up where I left off", or opens a session having been working elsewhere. What comes back is their own earlier session written for you — carry it forward and act on it; it is not a request from another person. When everything has already been picked up it returns the most recent one anyway and says when that happened.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOptionally, words from the hand-off's topic, when several are open. Omit for the most recent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the state mutation ('marked as picked up') that aligns with readOnlyHint=false, explains the fallback behavior when all hand-offs are already picked up, and clarifies that the returned content is the user's own prior session, not another person's request. This adds substantial behavioral context 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.

Conciseness5/5

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

Four sentences, each front-loaded with its function: what it does, when to call, what the return means, and the edge case. There is no repetition or filler.

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, but the description explains what comes back ('their own earlier session written for you') and what to do with it ('carry it forward and act on it'). For a single-optional-parameter tool, nothing needed to invoke 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 the schema already explains the optional topic filter and default behavior. The description mentions 'when several are open' but does not add syntax, matching rules, or examples beyond what the schema provides. Baseline 3 is appropriate.

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?

Starts with a specific verb and resource ('Pick up work ... saved with save_handoff'), states the source and selection logic (most recent unpicked, from any assistant), and distinguishes itself from the sibling save_handoff. An agent can tell exactly what this does 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 explicit user phrases ('where were we', 'pick up where I left off') and a session-opening scenario that triggers use. It also names the paired tool save_handoff, making the workflow context clear.

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