AI Loop Library MCP

Overview Schema Source Related Servers Discussions Admin

get_loop

Read-onlyIdempotent

Fetch a loop's full spec by id or slug: objective, trigger, actions, verification strength, stop condition, budget, approval boundary, prompt, and URL. Use after browsing or searching loops.

Instructions

Fetch one loop's full spec by id or slug: objective, trigger, allowed actions, verification (+ verifier strength), stop condition, budget, approval boundary, copyable prompt, and canonical URL. Use after browse_catalog or search_loops.

Input Schema

Name	Required	Description	Default
`id_or_slug`	Yes	Loop id, e.g. 'ci-optimization', or its title

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`title`	Yes
`summary`	Yes
`category`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.0Oct 4, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "category",
+    "url",
+    "summary"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint), so the bar is lower; the description still adds value by disclosing the depth of the payload, including verifier strength and approval boundary. It stops short of noting error behavior for unknown ids/slugs or whether the response is cached.

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?

Two compact sentences, front-loaded with the action and the returned surface, ending with the routing hint. No filler or repetition.

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 an output schema present, the description need not explain return values, yet it usefully summarizes them; the single required parameter is fully documented in the schema. Nothing an agent needs to invoke this correctly is missing.

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% on the single parameter, so the baseline is 3. The description says 'by id or slug' while the schema documents 'id ... or its title', a mild inconsistency that adds no disambiguating detail beyond the schema.

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 ('Fetch') and resource ('one loop's full spec') and enumerates exactly what is returned: objective, trigger, verification, stop condition, budget, approval boundary, prompt, canonical URL. This is clearly distinguishable from siblings like browse_catalog and search_loops.

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?

'Use after browse_catalog or search_loops' gives explicit sequencing context, telling the agent when this tool is the right next step. It does not, however, name an exclusion or an alternative for the case where the agent already knows the identifier directly.

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

Deploy Server