Skip to main content
Glama
paultaki

AI Loop Library MCP

by paultaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

catalog_stats

Read-onlyIdempotent

Retrieve an overview of available work loops: counts, categories, featured items, last update, and library source for quick inspection.

Instructions

Catalog overview: loop count, categories, featured loops, last_updated, and where the catalog was loaded from.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
loop_countYes
catalog_sourceYes
catalog_statusYes
category_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "catalog_source": {
+      "type": "string"
+    },
+    "catalog_status": {
+      "properties": {
+        "age_seconds": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "source": {
+          "type": "string"
+        },
+        "stale": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "stale",
+        "source",
+        "age_seconds"
+      ],
+      "type": "object"
+    },
+    "category_count": {
+      "type": "integer"
+    },
+    "loop_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "loop_count",
+    "category_count",
+    "catalog_source",
+    "catalog_status"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety and repeatability are covered without description help. The description adds that results describe the catalog's provenance ('where the catalog was loaded from'), which is genuine context, but it does not disclose freshness guarantees or whether last_updated reflects load time or content change.

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 fragment that lists only relevant fields, with no filler. It is a noun phrase rather than a sentence, which is terse but marginally less readable than a stated verb would be.

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?

An output schema exists, so the return shape need not be explained further, and with zero parameters there is no invocation nuance to cover. For a no-arg read-only stats tool, the description is sufficient.

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?

The tool takes zero parameters, so the baseline of 4 applies. There is no parameter semantics to explain and the description correctly avoids inventing any.

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 concrete resource (the catalog) and enumerates the exact payload: loop count, categories, featured loops, last_updated, and load origin. It is distinguishable from browse_catalog, search_loops, and list_categories, though it never uses an explicit verb like 'returns' or 'reports', leaving the action slightly implicit.

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 call this versus siblings. An agent cannot tell from the text whether this should precede browse_catalog/scarch_loops or how it relates to list_categories, which overlaps on the 'categories' output. No prerequisites or exclusions are given.

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