Skip to main content
Glama

Give a Brain Dump an outcome

triage_brain_dump
Idempotent

Resolve captured thoughts by choosing promote, park, or reject, with a mandatory rationale saved to the original dump.

Instructions

Closes the anti-dust loop. Choose promote to create a linked Boardroom Job, park to keep the thought with a deliberate later decision, or reject to close it. A rationale is mandatory and is saved on the original dump. This tenant-scoped action is available to every connected AI account and does not require superuser status. agent_id required.

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": {
      "agent_id": "<agent_id>",
      "brain_dump_id": "<brain_dump_id>",
      "decision": "<decision>",
      "rationale": "<rationale>"
    },
    "name": "triage_brain_dump"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes
decisionYes
priorityNonormal
rationaleYesShort reason for the outcome (max 1000 chars).
brain_dump_idYes
assigned_to_agent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare non-readonly, non-destructive, idempotent, closed-world behavior. The description adds meaningful side-effect context: promote creates a linked Boardroom Job, park retains the thought for later, reject closes it, rationale is persisted, and the action is tenant-scoped with no superuser requirement.

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 four tight sentences and front-loads the outcome and decision options. Product jargon like 'anti-dust loop' and 'Boardroom Job' is slightly opaque but does not waste space.

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

Completeness3/5

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

There is no output schema, and the description does not explain what the call returns or whether a linked job identifier is exposed. It covers the main decision semantics and authorization context but leaves priority/assignment behavior and preconditions incomplete for a six-parameter mutation.

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 only 17%, so the description must carry parameter meaning. It explains decision, rationale, and that agent_id is required, but priority and assigned_to_agent_id are completely unmentioned, and brain_dump_id is only implicit, leaving important semantics undocumented.

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 action: applying an outcome/decision to a brain dump, with clear meanings for promote, park, and reject. It distinguishes this as the closing/triage step relative to dump-creation or listing siblings, though it does not explicitly name those siblings.

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?

Explains the decision choices and the mandatory rationale, implying this is used after a brain dump exists and before later follow-up work. It gives no explicit when-not guidance, prerequisites, or named alternatives such as brain_dump or list_brain_dumps.

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