Skip to main content
Glama
Sign In
ai-dememory

ai-dememory

by GonzaloTorreras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Write Working Handoff

memory.working_handoff

Generate a Markdown handoff document after secret scanning, capturing current working context to transfer to another team member.

Instructions

Write a generated working/handoffs/ Markdown handoff after secret scanning.

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": {
      "title": "<title>",
      "notes": "<notes>"
    },
    "name": "memory.working_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYes
titleYes

Output Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already indicate read-only=false and destructive=false; description adds that the handoff is 'generated' but does not elaborate on side effects or prerequisites beyond the secret scanning context.

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?

A single sentence with no extraneous information; appropriately concise.

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?

Given the existence of an output schema and many sibling tools, the description does not explain the tool's role in a workflow (e.g., required prior steps like secret scanning) or return value semantics.

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?

With 0% schema description coverage, the description should explain parameters but does not mention title or notes, leaving the agent uncertain about how to fill them.

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 clearly states the action (write) and resource (working handoff) with context (after secret scanning), but does not explicitly differentiate from sibling tools like memory.write_proposal.

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?

It implies usage after secret scanning, providing some context, but lacks explicit when-not-to-use or alternative tools.

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