Skip to main content
Glama

List loops

list_loops
Read-onlyIdempotent

List all loops in the user's DoLoop account, each with its ordered queue of tasks and current_task_id.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, and closed-world, so the safety profile is covered. The description adds useful return context by mentioning ordered task queues and current_task_id, but it does not discuss pagination, result size, permissions, or ordering of the loops themselves.

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

Conciseness5/5

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

The definition is a single, front-loaded sentence with no filler. Every clause contributes either scope ('all loops in the user's account') or return-content information.

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?

With no output schema, the description must carry return-value information, and it does so only partially: it mentions ordered task queues and current_task_id but not loop identity fields, pagination behavior, or what 'all' means at scale. For a simple no-parameter list tool this is adequate but not fully complete.

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?

This tool has zero parameters, so there is no parameter semantics burden. The description correctly avoids irrelevant parameter discussion and instead uses the space to describe returned content.

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 uses a specific verb and resource: 'List all loops in the user's DoLoop account.' It also clarifies the returned content by mentioning each loop's ordered task queue and current_task_id. It does not explicitly distinguish itself from get_loop or list_tasks, but the plural/all scope makes the distinction largely clear.

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?

Usage is implied by 'List all loops,' suggesting this is the broad enumeration tool rather than a single-loop lookup. However, it does not explicitly say when to use this instead of get_loop or list_tasks, nor does it state any exclusions or prerequisites.

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