Skip to main content
Glama
Sign In
moamcp

moamcp

by Yorha9e
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

moa_board_delete

Delete a board key so it disappears from read and list operations, while preserving the deletion record in the append-only JSONL.

Instructions

Tombstone-delete a key: it disappears from read/list; the append-only JSONL keeps the deletion record.

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": {
      "key": "<key>"
    },
    "name": "moa_board_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
scopeNoBoard scope: "workspace" (default — persisted, shared by all sessions of this project), "global" (persisted, cross-project), or "task:<task_id>" (debate-local, archived with the task).
authorNoWho writes this entry (default "anonymous"). Subagents should pass their own agent id.
workspaceNoOptional absolute project path for workspace scope; omitted keeps the server workspaceCwd default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.13.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that this is a tombstone delete: the key disappears from reads/lists but the deletion record is retained in the append-only JSONL. This is useful context, though it does not mention permissions or reverse operations.

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?

The description is a single efficient sentence that front-loads the core action ('Tombstone-delete a key') and packs in the key behavioral detail. Every word earns its place, with no redundancy.

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

Completeness4/5

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

For a delete tool, the description adequately explains the deletion semantics and the append-only record, covering the main behavioral context. Since there is no output schema, some return-value detail could be added, but the description is fairly complete given the tool's simplicity.

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?

The schema already provides descriptions for scope, author, and workspace (75% coverage), leaving only 'key' undocumented. The description does not add further parameter semantics beyond naming 'a key', so it stays at the baseline for high schema coverage.

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 uses a specific verb 'tombstone-delete' and identifies the resource 'key', clearly distinguishing it from sibling read/write/list tools. It also explains the observable effect: the key disappears from read/list while the deletion record remains.

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?

Usage is implied by the tool name and description, but there is no explicit guidance on when to use this tool versus alternatives such as moa_board_write or moa_board_wait. No exclusions or prerequisites are 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