Skip to main content
Glama

list_decisions

Retrieve a project's decisions newest first, including the question, chosen answer, user's words, current status, and console origin, to review or relay them to stations.

Instructions

What the person decided on the project, newest first: the question, their words, the choice, whether it stands from now on and whether it matched what they typed (via "console": they answered or allowed it in the console; a permission they allowed there restarts that station with it). Follow them; relay them to stations by quoting the words.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: results are ordered newest first, decisions carry a standing/validity flag and a match flag, and the `via: console` value means the person answered or allowed it there, which restarts that station. It omits safety/read-only framing, pagination or result-size limits, and permission requirements for a tool that returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It front-loads the substantive content, but the sentence is a dense run-on with a nested parenthetical about the `via` console case that is hard to parse. Little is outright wasteful, yet the structure obscures rather than clarifies.

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

Completeness3/5

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

An output schema exists, so the lengthy enumeration of returned fields is largely redundant, while the genuinely ambiguous part (the project filter and its empty default) goes unexplained. For a simple list tool this is workable but not complete.

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?

The single `project` parameter has 0% schema description coverage, and the description only echoes 'on the project' without explaining format, whether an empty default means all projects, or how filtering behaves. For a one-parameter tool at zero coverage, the description should have closed that gap and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it surfaces 'what the person decided on the project, newest first' with fields like the question, their words, and the choice, so an agent can infer this is a list of decisions. But it never states the action plainly ('list decisions for a project') and spends most of its length on field semantics rather than purpose, so it reads more like a return-value spec than a tool description.

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

Usage Guidelines2/5

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

'Follow them; relay them to stations by quoting the words' is a downstream workflow hint, not a when-to-use rule. There is no guidance on when to call this versus list_assumptions or list_findings, and no indication of what happens with the default empty project filter.

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