Skip to main content
Glama

Get a loop

get_loop
Read-onlyIdempotent

Get one loop with its ordered queue of tasks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "loop_id": "<loop_id>"
    },
    "name": "get_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
loop_idYesThe loop's id (from list_loops).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that — the returned loop carries its ordered task queue — but says nothing about error behavior for a missing loop_id or about ordering semantics beyond the word "ordered".

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 with zero filler, but it is at the terse end for a tool with no output schema to fall back on.

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?

For a simple one-parameter read this is close to adequate, and the brief mention of the returned task queue partially compensates for the missing output schema. It still leaves the return shape (task fields, ordering guarantees, empty-queue case) underspecified.

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 100% and the loop_id parameter already documents itself as coming from list_loops, so the schema carries the parameter burden. The description adds no further meaning about the identifier.

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 ("Get one loop") and adds the meaningful detail that the result includes an ordered queue of tasks. The word "one" distinguishes it from a listing tool like list_loops without needing to name it, though no sibling is explicitly referenced.

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?

No guidance on when to reach for this tool versus list_loops or the task-level tools such as get_task, and no prerequisites or exclusions are stated. The reader must infer that this is the single-loop fetch.

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