Skip to main content
Glama
Sign In
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Log Decision

create_decision

Log a decision with status (decided, proposed, revisit) and optionally link it to a feature, release, or objective. Returns the decision.

Instructions

Log a decision and return it. status is 'decided' (default) | 'proposed' | 'revisit'; a 'decided' one stamps the decision time. Optionally weld it to a feature / release / objective via link_type + link_id (verified in-org). Only title is required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "Ship SSO before mobile",
      "link_id": "feat_123",
      "link_type": "feature",
      "rationale": "Enterprise deals need it"
    },
    "name": "create_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThe decision in a line (required).
statusNoDecision status (optional; default 'decided').
link_idNoId of the linked feature/release/objective, from list_features / list_releases / list_objectives (optional).
link_typeNoWhat it's linked to (optional; pair with link_id).
rationaleNoWhy — the reasoning (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14
  2. Removedv0.1.13
  3. Addedv0.1.6

TDQS

A4.4/5.0
Behavior4/5

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

Annotations provide no behavioral hints (all false), so the description carries the burden. It adds meaningful context: the default status of 'decided' and that a 'decided' status stamps the decision time, plus that link_type + link_id are verified within the organization. This goes beyond the schema and gives the agent useful behavioral expectations. It could mention idempotency or error handling, but the disclosed behaviors are valuable.

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?

The description is two concise sentences with no fluff. It front-loads the primary purpose, then efficiently covers status behavior, linking, and required fields. Every sentence earns its place and does not repeat schema details.

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?

With five parameters, no output schema, and no annotation hints, the description does well to cover the required field, status options, linking constraints, and validation. It explains behavior not obvious from the schema (time stamping). It could be slightly more complete by stating what the return value looks like, but 'return it' implies the created decision. Overall, it is sufficiently complete for an agent to invoke 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 description coverage is 100%, so the schema already defines each parameter. The description adds extra semantics beyond the schema: the default status value, the timestamp stamping behavior for 'decided', and the requirement that link_type and link_id must be paired and are verified in-org. This enrichment elevates the score above the baseline of 3.

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 'Log a decision and return it,' which clearly specifies the verb (log) and resource (decision). It distinguishes from sibling tools like update_decision and list_decisions by emphasizing creation. The mention of statuses and optional linking further clarifies the exact scope.

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?

The description clearly indicates when to use the tool: to create a decision. It states 'Only title is required' and outlines optional linking to features/releases/objectives, giving the user a sense of the typical invocation. However, it does not explicitly contrast with update_decision or list_decisions, though the context implies it. This warrants a 4 rather than a 5.

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