FlowState Hosted

manage_handoffs

Notes from one AI to the next. leave: before you end, if you stop mid-task, save where_i_was and next_step; the next start_here shows it after the hard rules. pickup: once you continue from a note, mark it so it stops showing. list: open notes. Not a session summary and not a todo. Adds or marks notes; never deletes. Returns the note or {notes}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "project": "<project>"
    },
    "name": "manage_handoffs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	list: max notes. Default 20.
`model`	No	Model name if known. Never guess.
`action`	Yes	The operation; see the tool description.
`project`	Yes	Project name or id. Required.
`next_step`	No	leave: the next step. Max 500 chars.
`handoff_id`	No	pickup: the note id.
`where_i_was`	No	leave: progress so far. Max 1,000 chars.
`include_picked_up`	No	list: include picked-up notes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only say the tool is non-read-only, non-destructive and non-idempotent; the description goes further by stating it "Adds or marks notes; never deletes" and that pickup makes a note "stop showing", plus it declares return values ("the note or {notes}"). The one gap is that the cost of a repeated pickup/leave and any visibility across projects is not spelled out.

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 identity sentence followed by action-scoped clauses in the same order as the enum; every sentence carries information. It is telegraphic and dense, but nothing is padding and the exclusions earn their place.

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 naming the return shape. For an eight-parameter, three-action tool with required project and a full-coverage schema, the description covers lifecycle, exclusions, and return, leaving nothing an agent needs missing.

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 the baseline is 3, but the description still adds meaning by pairing parameters to actions: where_i_was and next_step belong to leave, handoff_id is the note to mark on pickup, and the effect of pickup (note stops showing) is described rather than just "the note id". limit and include_picked_up are left to the schema.

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?

Opens with a concrete identity ("Notes from one AI to the next") and then defines each of the three actions with a specific verb and payload. It explicitly distinguishes itself from siblings by naming start_here and ruling out session summaries and todos, so an agent can separate it from manage_sessions/manage_todos without inspecting schemas.

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 when-to-use rules per action: leave only "if you stop mid-task", pickup "once you continue from a note", list for open notes. It also names the negative cases ("Not a session summary and not a todo") and the downstream consumer (start_here shows the note after the hard rules).

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

All FlowState Hosted 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?