Skip to main content
Glama
Sign In
Loopy MCP Server

Loopy MCP Server

by hotkid61
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_loop

Audit agent loops to identify weaknesses, verify stopping conditions, and receive actionable improvement suggestions.

Instructions

Audit a loop for weaknesses, check stopping conditions, and suggest improvements

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

Input Schema

NameRequiredDescriptionDefault
loop_promptYesThe loop prompt/instructions to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions audit and suggestions but does not state whether the tool modifies any data, whether it requires an existing loop, or what the output format is. The verb 'audit' implies read-only but is not explicit.

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 description is a single 13-word sentence, clear and front-loaded. It conveys essential actions without waste, though it could benefit from additional structure.

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 tool with one parameter and no output schema, the description is moderately complete. It lacks details about what the tool returns or whether it requires the loop to be saved, but the core function is clear.

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% with a description for loop_prompt. The description adds context that analysis covers weaknesses, stopping conditions, and improvements, but does not elaborate on expected format or constraints of the prompt parameter.

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 specifies auditing a loop for weaknesses, checking stopping conditions, and suggesting improvements. It distinguishes from sibling tools like craft_loop, run_loop, and discover_patterns by focusing on analysis rather than creation or execution.

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 alternatives such as get_loop_recommendations or get_loop_details. Does not specify prerequisites or context for use.

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