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

memory-bank-mcp

by gcorroto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

memorybank_complete_task

Mark a task as completed, supporting both internal (TASK-) and external (EXT-) task IDs for a given project.

Instructions

Marca una tarea como completada. Funciona tanto para tareas internas (TASK-) como externas (EXT-).

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": {
      "projectId": "<projectId>",
      "taskId": "<taskId>"
    },
    "name": "memorybank_complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesID de la tarea a completar (ej: 'EXT-123456', 'TASK-789012')
projectIdYesIdentificador único del proyecto (OBLIGATORIO)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.15

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It states the action (mark as completed) but does not mention side effects, irreversibility, permissions, or whether it triggers notifications. For a mutation tool, this is insufficient.

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?

Two sentences with no filler. Every word contributes to the meaning. The structure is front-loaded and efficient.

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?

Without annotations or output schema, the description lacks return value, error conditions, prerequisites (e.g., task must be open), and how it interacts with other tools. For a simple action, it could be adequate, but with 18 siblings, more context is needed.

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 documents both parameters. The description adds that the tool works for both TASK-* and EXT-* task IDs, which is slightly redundant with the schema's taskId description but provides confirmation.

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?

The description clearly states the verb 'Marca' and the resource 'tarea como completada', and specifies it works for both internal (TASK-*) and external (EXT-*) tasks. This distinguishes it from siblings like claim_task, delegate_task, or route_task.

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?

The description implies usage when a task is completed, but provides no explicit guidance on when to use this tool versus alternatives. There are siblings like claim_task and delegate_task, but no comparison or exclusion criteria.

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