Skip to main content
Glama

list_assumptions

Retrieve a project's assumptions in priority order, including each question, choice, rationale, tickets, and current state; filter by state to review what remains open, kept, or overturned.

Instructions

The project's assumptions, A1 first: the question, the choice, why, the tickets, and the state (open: not yet confirmed; kept; overturned, with the person's words). state narrows the list.

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_assumptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.2/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: ordering ('A1 first') and the meaning of each state value, including that 'overturned' carries the person's words. It says nothing about permissions, pagination, or whether the list is scoped to a current project by default, which are meaningful gaps for an unannotated tool.

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?

A single dense sentence that front-loads the resource and then lists the returned fields and filter semantics. The nested parentheticals make it slightly hard to parse, but no sentence is wasted.

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 return-value detail is partly redundant, and the description adds the ordering and state semantics that the schema lacks (no enums are declared). However, the undocumented `project` parameter and the absence of default-scoping behavior leave an agent guessing how to call it correctly.

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 coverage is 0%, so the description must compensate. It does well for `state`, explaining that it narrows the list and enumerating the values open/kept/overturned, but the `project` parameter is never mentioned — it's unclear whether it defaults to the current project or must be supplied.

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

Purpose4/5

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

The description names the resource (the project's assumptions) and enumerates the fields returned (question, choice, why, tickets, state), so an agent knows this is a list/read operation over assumptions. It doesn't explicitly contrast with related siblings such as list_decisions or decide_assumption, but the resource is specific enough to distinguish it.

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?

'`state` narrows the list' is the only usage cue, implying the tool can be used to retrieve all assumptions or a filtered subset. There is no guidance on when to prefer this over assume or decide_assumption, nor on what the unfiltered default returns.

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