Skip to main content
Glama

List workflow states

list_workflow_states
Read-only

Lista los workflow states (estados) disponibles con su id, nombre, type, team, position (orden en el tablero), unblocksDependents (si una bloqueadora en ese estado deja de bloquear, p. ej. In Review) y wipLimit (límite de issues, null si no hay). Necesario para obtener el stateId al crear o cambiar de estado una issue. workspaceId opcional: el workspace donde operar (list_workspaces los enumera). Sin él se usa el de la credencial.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the description's job is lighter. It still adds real behavioral detail: the meaning of each returned field, the "null si no hay" semantics for wipLimit, the unblocksDependents semantics with the In Review example, and the credential-based workspace fallback. It does not discuss pagination or ordering guarantees of the returned list itself.

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 and every clause carries information — the parenthetical field glosses explain return values, and the final two sentences cover the parameter. It is dense but somewhat over-packed into long parenthetical runs, which slows scanning slightly.

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

Completeness5/5

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

With one optional parameter and no output schema, the description must explain both the call and the shape of the result, and it does — fields, null semantics, and the default workspace resolution are all covered. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter alone, and it does: workspaceId is explicitly optional, defined as the workspace to operate in, linked to list_workspaces for discovery, and given an explicit default ("Sin él se usa el de la credencial"). That is more than the bare schema provides.

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?

States a specific verb ("Lista") and resource ("workflow states") and enumerates exactly which fields come back (id, nombre, type, team, position, unblocksDependents, wipLimit). That field list distinguishes it from generic list siblings and tells an agent what data it will receive before it ever calls the tool.

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?

"Necesario para obtener el stateId al crear o cambiar de estado una issue" gives an explicit trigger for calling it, tied to the create/change-state workflows. It also routes workspace enumeration to list_workspaces. What it lacks is any when-not condition or note about caching/reuse, but the intended usage context is unambiguous.

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