Skip to main content
Glama

list

Retrieve current strategy positions under Playing to Win boxes to evaluate tasks against adopted positions, enabling triage and prioritization; optional cascade filters by strategy.

Instructions

The strategy: every current position under its Playing to Win box, aspiration first; optional cascade (a key from cascade_list) for one strategy, or "-" for the positions no cascade holds. To sort, triage or prioritise tasks in any tracker: call list first and judge each task against the ADOPTED positions only; if none is adopted, stop and say so. Keep what serves one, park what doesn't, and name the position that decided it. Ask before changing anything in the tracker, and never delete a task.

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

Input Schema

NameRequiredDescriptionDefault
cascadeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but does not clearly state whether the tool itself is read-only, what permissions are required, or what side effects it has. The instructions to 'ask before changing anything' and 'never delete a task' describe agent behavior after listing, not the tool's own mutation profile.

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?

The purpose is front-loaded in the first sentence, and the subsequent sentences provide usage-focused guidance. It is information-dense but not bloated; the main weakness is that it mixes listing semantics with a triage workflow, making some sentences feel more like process instructions than tool definition.

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 values need not be explained. However, for a tool with no annotations, the description leaves key behavioral context unstated, such as read-only status and permission requirements, and it relies on undefined domain terms like 'Playing to Win box' and 'ADOPTED positions'.

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 0%, so the description must explain the cascade parameter, and it does: it is a key from cascade_list, or '-' for positions no cascade holds, with omission implying all current positions. It adds substantial meaning beyond the bare schema, though it could more explicitly define the empty-string default.

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 states a specific verb and resource: it lists every current strategy position under its Playing to Win box, aspiration first, with an optional cascade filter. This distinguishes it from a generic list tool, though the jargon-heavy framing and lack of explicit contrast with siblings like cascade_list or show keep it from a 5.

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?

It gives clear when-to-use guidance: call list first when triaging tasks, judge only against ADOPTED positions, and stop if none is adopted. It does not explicitly name when to avoid this tool or which sibling to use for related queries, but the workflow context is strong.

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