Skip to main content
Glama

decide

Append a decision and its reason to the project's decision log for non-obvious choices such as libraries or trade-offs, so later sessions do not re-litigate it.

Instructions

Append a decision with its reason to the project's decision log. Use when a non-obvious choice is made (library, data model, trade-off) so a later session does not re-litigate it.

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": {
      "decision": "<decision>"
    },
    "name": "decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNo
decisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the write is additive (append) and that the record persists across sessions, which is meaningful context, but it says nothing about permission requirements, whether duplicates are rejected or merged, or whether the decision log is scoped to an ambient project or needs to be identified.

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: the first establishes the action and destination, the second the trigger and payoff. The action is front-loaded, and every clause carries information.

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 two-parameter append tool with no output schema and no annotations, the definition covers what it does, when to call it, and why the record matters. The main omission is operational context such as which project the log belongs to and whether a missing 'why' is acceptable, but nothing essential to invoking it correctly is absent.

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 0%, so the description must compensate, and it only partially does: 'with its reason' implies the 'why' field is the rationale attached to 'decision', which is genuinely useful mapping. It adds nothing about expected format, length, or the significance of 'why' being optional while 'decision' is required.

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) against a specific resource (the project's decision log) with the payload it carries (a decision plus its reason). This reads clearly as the write counterpart to the read-only 'decisions_list' sibling, so an agent can distinguish them without opening either schema.

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

Usage Guidelines4/5

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

Gives an explicit trigger condition with concrete examples (library, data model, trade-off) and a rationale for logging (a later session does not re-litigate it). It does not name a when-not condition or an alternative tool, but the inclusion criteria are unusually concrete for a short definition.

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