Skip to main content
Glama
fenbs-ai

fenbs-mcp

Official

fenbs_add_decision

Record decisions, open questions, or standing rules on a fenbs board. Use it to capture what a person decided, ask for a decision, or set a rule that always or never applies.

Instructions

Record a decision, or ask a question for a person to decide. This is also how a RULE is recorded: a rule is a decision that holds from now on (standingRule true). When the person you work for says how something must always, or never, be done, record it here -- status decided, standingRule true, them in deciders, their words quoted in reason -- never as a context note. You may write a decision down; you never make one: record decided only when a person decided it. When nobody has decided yet, add it as open (the default) and ask. To change a rule, record a new decision with supersedes. Search fenbs_list_decisions first. Link the tasks that depend on it with tasks. Needs permission to change tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoProduct, Technical, Commercial & pricing, Legal & compliance, Operational, Design, People, Other -- or the board's own.
tasksNoRefs of tasks to link to it.
titleYesThe decision, or the question, in one line.
reasonNoWhy. Quote the person who decided where you can.
statusNoopen: a question for a person to decide (the default). proposed: a recommendation, not agreed. decided: a person decided it -- needs decision and who decided. superseded / reversed / withdrawn: it no longer holds.
contextNoThe question, and why it came up.
projectNoA project on this board, by name. Leave it out for the whole board.
decidersNoWho decided -- people, never you. Each is { me: true } for the person you work for (the usual case: they told you), a board member by the email they sign in to fenbs with, or somebody outside the board by name and role.
decisionNoWhat was decided. Needed before status decided; empty while it is open.
reviewByNoyyyy-mm-dd, optional.
decidedOnNoyyyy-mm-dd, the day it was decided -- may be before today. Defaults to today when decided.
supersedesNoThe decision this replaces, e.g. DEC-003. When this one is decided, that one becomes superseded.
standingRuleNotrue makes it a RULE: it holds from now on, not just this once. Rules are shown in full at the top of every assistant's AI context and every assistant must follow them. Use it whenever the person says how something must always, or never, be done.
optionsConsideredNoThe alternatives, and why they were not chosen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it delivers: standingRule consequences (shown at the top of every assistant's AI context and mandatory to follow), the supersedes side effect (the replaced decision becomes superseded), the open default, and a permission requirement ('Needs permission to change tasks'). It also clarifies the authority boundary that the agent records but never makes decisions.

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?

Purpose and the rule-vs-question distinction are front-loaded, and each sentence carries operative guidance. It is longer than strictly necessary and some phrasing is repetitive, but there is little dead weight.

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?

For a 14-parameter mutation tool with no annotations and no output schema, the description covers the decision lifecycle, defaults, side effects, prerequisites, and required permissions, leaving nothing critical for correct invocation unaddressed.

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 workflow-level meaning beyond the schema by prescribing the coordinated use of fields (status decided + standingRule true + them in deciders + quoted reason) and by explaining the supersedes linkage when the new decision is decided.

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 opens with a precise verb+resource pair ('Record a decision, or ask a question for a person to decide') and immediately disambiguates the rule case. An agent can distinguish this from fenbs_add_context_note and fenbs_update_decision without opening any 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?

It states explicit conditions: record as a rule when the person says how something must always/never be done, 'never as a context note'; record decided only when a person decided it; add as open and ask when nobody has decided. It names fenbs_list_decisions as a prerequisite ('Search ... first') and names the context-note alternative to avoid.

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