PCFHub

List PCF controls

list_components

Read-onlyIdempotent

Browse the PCFHub catalog by category, tag, author, control type, host or text, paged and sorted. Use it to enumerate or narrow the catalog; use search for a plain-language question about what a control should do, and get_component for one control in full. Filters take slugs, which list_taxonomy supplies. Nothing here fails on bad input: an unrecognised sort falls back to the default, and filters matching nothing return an empty page — so read total and sort from the result rather than assuming the filters applied.

Input Schema

TableJSON Schema

Name	Required	Description
`host`	No	Where the control has to run. A control supporting both hosts matches either.
`page`	No	Defaults to 1.
`sort`	No	Defaults to relevance when there is a query, newest otherwise.
`tags`	No	Tag slugs, from list_taxonomy. A control must carry every tag given.
`query`	No	Words to match against names, taglines and descriptions.
`author`	No	An author slug, from list_taxonomy.
`category`	No	A category slug, from list_taxonomy.
`per_page`	No	Defaults to 24; at most 48.
`control_type`	No	field binds one column on a form; dataset renders a view; virtual is a React control; grid_customizer changes how an editable grid renders cells.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	The page returned.
`sort`	Yes	The sort actually applied, which is the default when none was given or the one given was not recognised.
`total`	Yes	Controls matching the filters, across every page.
`perPage`	Yes
`lastPage`	Yes	The highest page number for these filters.
`components`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 19, 2026

addedInput schema / properties / host

Added value: +{
+  "description": "Where the control has to run. A control supporting both hosts matches either.",
+  "enum": [
+    "canvas",
+    "model-driven"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / components / items / properties / hosts

Added value: +{
+  "description": "Where this control runs. Empty only where nobody has declared it.",
+  "items": {
+    "enum": [
+      "canvas",
+      "model-driven"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / components / items / required

Previous value: -[
-  "slug",
-  "name",
-  "controlType",
-  "category",
-  "author",
-  "downloadCount",
-  "url"
-]New value: +[
+  "slug",
+  "name",
+  "controlType",
+  "hosts",
+  "category",
+  "author",
+  "downloadCount",
+  "url"
+]

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "components": {
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Author slug.",
+            "type": "string"
+          },
+          "category": {
+            "description": "Category slug.",
+            "type": "string"
+          },
+          "controlType": {
+            "enum": [
+              "field",
+              "dataset",
+              "virtual",
+              "grid_customizer"
+            ],
+            "type": "string"
+          },
+          "downloadCount": {
+            "type": "integer"
+          },
+          "latestVersion": {
+            "description": "Null where nothing has been released yet.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "description": "Pass to get_component.",
+            "type": "string"
+          },
+          "tagline": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Absolute URL of the control's page.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "controlType",
+          "category",
+          "author",
+          "downloadCount",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lastPage": {
+      "description": "The highest page number for these filters.",
+      "type": "integer"
+    },
+    "page": {
+      "description": "The page returned.",
+      "type": "integer"
+    },
+    "perPage": {
+      "type": "integer"
+    },
+    "sort": {
+      "description": "The sort actually applied, which is the default when none was given or the one given was not recognised.",
+      "type": "string"
+    },
+    "total": {
+      "description": "Controls matching the filters, across every page.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "page",
+    "perPage",
+    "lastPage",
+    "total",
+    "sort",
+    "components"
+  ],
+  "type": "object"
+}

First observedSep 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds meaningful behavior beyond that: unrecognized sorts fall back to defaults, unmatched filters return an empty page, and the caller should read `total` and `sort` rather than assuming filters applied. This is useful non-obvious runtime behavior.

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?

Four sentences, each earning its place: what it does, when to use alternatives, filter input requirements, and bad-input behavior. It is front-loaded with the core purpose and contains 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?

For a 9-parameter read-only list tool with an output schema present, the description covers enumeration, narrowing, sorting/paging, taxonomy slug provenance, and failure behavior. Nothing an agent needs to call or interpret this tool 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%, so the schema already documents every parameter and its defaults. The description adds the general rule that filters take slugs from list_taxonomy, which is useful, but most of that is also present in the schema descriptions. A baseline 3 is appropriate because the schema carries the heavy lifting.

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 names the exact resource (PCFHub catalog) plus the explicit facets it can filter by. It also distinguishes itself from search and get_component, so an agent can tell siblings apart without opening their schemas.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool ('enumerate or narrow the catalog') and when to use alternatives ('search for a plain-language question', 'get_component for one control in full'). It also tells the agent that filters require slugs supplied by list_taxonomy, which is a concrete prerequisite.

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

All PCFHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?