Skip to main content
Glama

List decision prompts

list_decision_prompts
Read-only

List decision-relief prompts (dilemmas Clara weighed in on) with their recommendation, filtered by status (default open). Read-only.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the trailing 'Read-only' sentence merely restates structured data rather than adding behavior. What the description does add is the semantic framing of a decision prompt and the default-open filter, but it says nothing about ordering, pagination, or whether recommendations are truncated.

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 front-loaded sentence carries the purpose, the concept definition, and the default filter, followed by a short safety note. The closing 'Read-only' is redundant with the annotations and is the only wasted fragment.

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?

This is a simple two-parameter read tool with annotations covering its safety profile and no output schema to explain, so the description is close to sufficient. The remaining gap is the unmentioned limit parameter and any hint about result ordering or volume.

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 carry the load; it partially does by explaining that filtering is by status and that open is the default. The second parameter, limit, is never mentioned in the description, and its interaction with the result set (page size, truncation) is undocumented.

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?

States a specific verb and resource ('List decision-relief prompts') and parenthetically defines the concept ('dilemmas Clara weighed in on') plus what is returned ('with their recommendation'). It does not, however, distinguish this from the sibling list_decisions, which an agent could easily confuse with it.

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

Usage Guidelines3/5

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

The description conveys the default state ('default open'), which implies the tool surfaces outstanding items unless told otherwise, but it gives no explicit when-to-use/when-not guidance and never points to an alternative for resolved items or for the other decision-listing tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources