Pipeworx

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

TableJSON Schema

Name	Required	Description	Default
`category`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description
`packs`	Yes
`gateway`	Yes	Gateway base URL
`total_packs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedAug 9, 2026
- 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"
```

Changed1 schema field changedAug 8, 2026

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."

Changed1 schema field changedMay 13, 2026

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"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {},
+  {
+    "category": "Finance"
+  }
+]

First observedApr 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Given annotations already declare readOnlyHint=true and destructiveHint=false, the description adds behavioral value by disclosing the return fields (pack names, categories, tool counts, gateway URLs) and the exploratory use case. It does not describe any limitations (e.g., pagination) but the provided annotations and return-field disclosure are sufficient context. No contradiction with annotations.

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?

The description is two sentences, front-loaded with the main action and purpose, followed by a concise usage note. Every sentence provides value with no redundancy or filler.

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?

For a simple listing tool with one optional parameter and an output schema, the description covers the main purpose, return contents, and usage intent. The schema fills in the parameter details. It is not overly verbose but sufficient for an agent to understand the tool's scope. It could have hinted at the optional category filtering in the description, but the schema covers this, so completeness is high.

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?

The schema has 100% coverage for the single optional 'category' parameter, with a detailed description explaining it is a free-text filter and not a fixed taxonomy. The description itself does not mention this parameter, but because the schema fully documents it, the baseline score of 3 is appropriate.

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?

The description uses a specific verb ('Browse') and resource ('Pipeworx packs'), and further specifies the return contents (pack names, categories, tool counts, gateway URLs). The phrase 'all available' distinguishes it from sibling tools like search_packs, which implies a search-oriented alternative.

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?

The description clearly states when to use the tool ('Use to discover data sources or explore what's available'), providing suitable context. It does not explicitly mention exclusions or alternatives, but the 'all available' wording implies a browse-all scenario, making it distinct from search tools. This is clear context but lacks explicit when-not guidance.

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

All Pipeworx tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.