Skip to main content
Glama
Sign In
warp-memory-mcp

warp-memory-mcp

by robertleelittleiii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_handoffs

Retrieve coordination handoffs between Grok and Oz agents. Filter by recipient to track cross-agent task transfers.

Instructions

List Grok ↔ Oz coordination handoffs.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
to_agentNoFilter by recipient (oz, grok).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure, but it only repeats the list semantics. It does not mention ordering, pagination, the default limit, whether results are filtered by recipient, or any side-effect expectations, leaving the agent to infer behavior from the schema.

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?

The description is a single efficient, front-loaded sentence with no filler. It is concise, though the brevity comes at the cost of omitting usage and behavioral details.

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

Completeness2/5

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

For a simple 2-parameter list tool this is close to adequate, but the absence of annotations, output schema, and any usage guidance leaves gaps in filtering behavior, result shape, and sibling-tool selection. A short phrase about when to use it or what the returned handoffs contain would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: to_agent has a schema description, but limit only has a type and default. The tool description adds no parameter meaning, so the semantics of limit rely entirely on its name and default value.

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?

The description states a clear action ('List') and a specific resource ('Grok ↔ Oz coordination handoffs'), and the plural verb distinguishes it from singular get_handoff or mutating write_handoff. It doesn't explicitly call out sibling tools, so it stops short of full differentiation.

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?

No guidance is provided about when to use list_handoffs rather than list_conversations, search, or get_handoff. The tool's purpose is implied only by its name and the verb, with no conditions or alternatives stated.

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

Deploy Server

Other Tools