Skip to main content
Glama
Sign In
Unified Memory MCP

Unified Memory MCP

by piligrim-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

handoff_complete

Mark a transferred task handoff as complete and add optional notes once the work is finished.

Instructions

Mark a handoff complete once the transferred task is finished.

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": {
      "id": "<id>"
    },
    "name": "handoff_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
notesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a state-changing mutation but says nothing about what completion does (archive, delete, status flip), whether it is idempotent, what permissions are needed, or what the idempotency/error behavior is on a repeated call.

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 efficient sentence with the action front-loaded and no filler. It is well-structured but under-specified rather than genuinely concise-with-substance.

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 mutation tool with no annotations, no output schema, and undocumented parameters, the description should explain the resulting state and how notes are used. It leaves the agent without enough to invoke it confidently beyond the happy path.

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 description coverage is 0% and the description never mentions either field. It gives no hint that "id" is the handoff identifier or what "notes" records, leaving the agent to infer both from the property names alone.

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?

States a specific verb and resource ("Mark a handoff complete") plus the triggering condition ("once the transferred task is finished"). An agent can tell it apart from handoff_save/handoff_load, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

The clause "once the transferred task is finished" implies the right moment to call it, but there is no explicit when-not guidance and no mention of alternatives such as handoff_save or handoff_list. Usage is inferred rather than 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