Skip to main content
Glama
sunsatosolutions

Vulcanus

by sunsatosolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Record a decision

append_decision

Append a confirmed decision to a project's Decisions note, in the vault's Decision/Details format. Only record what the operator has actually confirmed.

Instructions

Append a confirmed decision to a project's Decisions note, in the vault's Decision/Details format. Only record what the operator has actually confirmed. When it replaces an earlier decision, pass that decision's heading as supersedes: the new section records supersedes::, and the old one gains superseded-by:: and superseded-on:: under its heading but is otherwise left as history — never delete or rewrite the old decision yourself. Writes to disk: it adds to the end of the note, so calling it twice records the decision twice. Returns the note path and the heading written; errors when the project or its Decisions note is missing, or when supersedes names no live section (then nothing is written).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort heading for the decision
detailsNoOptional supporting details
projectYesProject name, id, or trigger word
decisionYesThe decision itself, one or two sentences
supersedesNoHeading of the existing decision this one replaces, if any

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.3
    • addedInput schema / properties / supersedes
      Added value: +{
+  "description": "Heading of the existing decision this one replaces, if any",
+  "type": "string"
+}
  2. First observedv0.4.4

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that this writes to disk, appends rather than replaces (matching non-idempotent behavior), never deletes or rewrites history even when superseding, and enumerates error conditions (missing project/note, dead supersedes target, nothing written). It does not spell out permission or concurrency behavior, so it is strong but not exhaustive.

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?

Front-loaded with the core action and side effects, and every sentence carries information (format, confirmation rule, supersede mechanics, disk behavior, return value, failures). It is dense and long, but not padded; a lighter touch on return/error detail would have tightened it further.

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

Completeness5/5

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

There is no output schema, yet the description compensates by naming the return payload (note path and heading written) and the failure modes. Combined with the mutation disclosures, an agent has everything required to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for supersedes: what value to pass, what markers get written where, and the non-destructive side effect on the older section. title/decision/project are only implicitly clarified.

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?

States a specific verb (Append) and resource (a confirmed decision to a project's Decisions note) plus the target format. The resource naming (decisions vs. the sibling append_rule's rules) makes it self-evidently distinct from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the operative precondition ('Only record what the operator has actually confirmed') and precise routing rules for the optional supersedes parameter, including the fact that a bad supersedes value writes nothing. It also warns that repeat calls duplicate the entry, which is exactly the when-not guidance an agent needs.

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