Skip to main content
Glama
Sign In
Loopy MCP Server

Loopy MCP Server

by hotkid61
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

run_loop

Execute a bounded agent loop by providing a prompt; set maximum passes and name for tracking, and get a receipt.

Instructions

Execute a loop with bounded passes and get a receipt

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_prompt": "<loop_prompt>"
    },
    "name": "run_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
loop_nameNoName of the loop for tracking
max_passesNoMaximum number of passes (default: 10)
loop_promptYesThe loop prompt to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description only mentions execution and receipt but does not disclose side effects, safety, or whether the loop execution is destructive or idempotent.

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?

Single sentence with no redundancy; front-loaded essential action and outcome.

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?

Simple tool with few params; description covers core purpose but lacks behavioral context that would be expected without annotations.

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 provides 100% param descriptions; description adds 'bounded passes' and 'receipt' but does not significantly extend beyond schema defaults.

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?

Description clearly states the tool executes a loop with bounded passes and returns a receipt, distinguishing it from sibling tools that analyze, craft, or retrieve loop details.

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 use this tool versus siblings like analyze_loop or craft_loop; misses explicit context for selection.

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

Deploy Server

Other Tools