Skip to main content
Glama

Start second-brain task envelope

second_brain_task_start
Idempotent

Log an auditable task-start envelope with goal, authority, and retrieval receipt to trace task provenance without writing sources or promoting knowledge.

Instructions

Append an auditable task-start envelope with authority and retrieval receipt. It never writes 01_Sources or promotes knowledge.

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": {
      "taskId": "<taskId>",
      "goal": "<goal>"
    },
    "name": "second_brain_task_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
sourceNo
taskIdYes
projectNo
taskTypeNo
authorityNo
retrievalNo

Output Schema

NameRequiredDescriptionDefault
recordYes
taskIdYes
createdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare write (readOnlyHint=false), non-destructive, idempotent, and closed-world behavior, so the bar is lower. The description adds genuine scope context - the envelope is auditable and does not touch 01_Sources or promote knowledge - but it is silent on what the idempotency guarantee means in practice (whether a repeated call with the same taskId overwrites or is a no-op) and on where the envelope is written.

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 tight sentences, with the core action front-loaded and the scope exclusion immediately after. Nothing is padded or repeated from the schema.

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?

An output schema exists, so return values need no explanation, but for a 7-parameter write tool with a nested object and zero schema documentation, the description is too thin. An agent cannot tell from it what a valid envelope requires or how the retrieval receipt relates to the retrieval object's fields.

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% across 7 parameters, including a nested retrieval object with query, receipt, and candidates, so the description must carry the burden. It gestures at two of them ('authority and retrieval receipt') but adds no meaning: no format, expected values, or distinction between goal, project, taskType, and source. The required taskId/goal pair is not mentioned at all.

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 names a specific verb and artifact: 'Append an auditable task-start envelope.' The bounded scope ('never writes 01_Sources or promotes knowledge') helps distinguish it from capture and upsert-card siblings, though the pairing with second_brain_task_finish is not explicitly addressed.

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 only implied by the name and the phrase 'task-start' - an agent can infer this is the opening half of a start/finish pair. There is no explicit when-to-use statement, no prerequisite (e.g., must taskId pre-exist?), and no named alternative such as second_brain_task_finish.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.