Skip to main content
Glama
Sign In

Pipeworx

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Packs

list_packs
Read-onlyIdempotent

Browse all available Pipeworx packs. Returns pack names, categories, tool counts, and gateway URLs. Use to discover data sources or explore what's available.

Input Schema

NameRequiredDescriptionDefault
categoryNoFree-text filter matched against pack slugs, descriptions, and tool names/descriptions — not a fixed taxonomy (e.g. "weather", "pesticide", "sec filings"). Omit to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "description": "The catalog of MCP packs this gateway serves.",
-  "properties": {
-    "gateway": {
-      "description": "Gateway base URL",
-      "type": "string"
-    },
-    "packs": {
-      "items": {
-        "properties": {
-          "description": {
-            "type": "string"
-          },
-          "gateway_url": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "slug": {
-            "type": "string"
-          },
-          "tool_count": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "slug",
-          "name",
-          "gateway_url"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total_packs": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "total_packs",
-    "gateway",
-    "packs"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed12 schema fields changed
    • addedOutput schema / description
      Added value: +"The catalog of MCP packs this gateway serves."
    • changedOutput schema / properties / gateway / description
      Previous value: -"Pipeworx gateway URL"New value: +"Gateway base URL"
    • removedOutput schema / properties / packs / description
      Removed value: -"List of available packs"
    • removedOutput schema / properties / packs / items / properties / category
      Removed value: -{
-  "description": "Pack category",
-  "type": "string"
-}
    • removedOutput schema / properties / packs / items / properties / description / description
      Removed value: -"Pack description"
    • removedOutput schema / properties / packs / items / properties / gateway_url / description
      Removed value: -"MCP gateway URL for the pack"
    • removedOutput schema / properties / packs / items / properties / name / description
      Removed value: -"Pack display name"
    • removedOutput schema / properties / packs / items / properties / slug / description
      Removed value: -"Pack identifier slug"
    • removedOutput schema / properties / packs / items / properties / status
      Removed value: -{
-  "description": "Pack operational status",
-  "type": "string"
-}
    • addedOutput schema / properties / packs / items / properties / tool_count
      Added value: +{
+  "type": "number"
+}
    • changedOutput schema / properties / packs / items / required
      Previous value: -[
-  "slug",
-  "name",
-  "description",
-  "category",
-  "status",
-  "gateway_url"
-]New value: +[
+  "slug",
+  "name",
+  "gateway_url"
+]
    • removedOutput schema / properties / total_packs / description
      Removed value: -"Total number of packs matching the filter"
  3. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category (e.g., Science, Finance, Games, Humor, Entertainment, Reference)"New value: +"Free-text filter matched against pack slugs, descriptions, and tool names/descriptions — not a fixed taxonomy (e.g. \"weather\", \"pesticide\", \"sec filings\"). Omit to list everything."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "gateway": {
+      "description": "Pipeworx gateway URL",
+      "type": "string"
+    },
+    "packs": {
+      "description": "List of available packs",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Pack category",
+            "type": "string"
+          },
+          "description": {
+            "description": "Pack description",
+            "type": "string"
+          },
+          "gateway_url": {
+            "description": "MCP gateway URL for the pack",
+            "type": "string"
+          },
+          "name": {
+            "description": "Pack display name",
+            "type": "string"
+          },
+          "slug": {
+            "description": "Pack identifier slug",
+            "type": "string"
+          },
+          "status": {
+            "description": "Pack operational status",
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "description",
+          "category",
+          "status",
+          "gateway_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_packs": {
+      "description": "Total number of packs matching the filter",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_packs",
+    "gateway",
+    "packs"
+  ],
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {},
+  {
+    "category": "Finance"
+  }
+]
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds real value by stating the return shape (pack names, categories, tool counts, gateway URLs), which no output schema provides, though it omits pagination or result-size behavior.

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?

Three short sentences, front-loaded with the action and return payload, with no filler. Tight and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so adequately for a read-only list tool with one optional filter. Only minor gaps remain around result volume and the natural next step into get_pack_tools.

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 schema itself explains the free-text category matching thoroughly (slugs, descriptions, tool names). The description adds nothing about the filter and even says "all available packs," mildly downplaying the optional category parameter. Baseline 3 applies.

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?

Clear verb+resource ("Browse all available Pipeworx packs") with the returned fields enumerated. However, it never distinguishes itself from the sibling search_packs, which appears to be the filtered/full-text variant, leaving an agent to guess which to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to discover data sources or explore what's available" implies a discovery use case but gives no when/when-not guidance and never names search_packs or get_pack_tools as the alternative for narrower or deeper queries.

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

All Pipeworx toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources