Skip to main content
Glama

PCFHub

by io.github.pcfhub
OverviewDiscussionsAdmin

Search PCFHub

search
Read-onlyIdempotent

Full-text search across every published PCF control and its documentation, ranked by relevance. Use it when you know what a control should do but not what it is called; use list_components instead to filter by category, tag, author or control type, and get_component when you already have a slug. Returns control and documentation hits, each with a snippet and a URL. A query that matches nothing is an empty result rather than an error, and a misspelling may be answered with results for a corrected spelling, which the result states.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many results to return. Defaults to 10.
queryYesWhat to look for, in plain words: "barcode scanner", "kanban", "date range".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
queryYesThe query as it was searched.
totalYesHow many results matched, which may be more than were returned.
correctedQueryNoSet only when nothing matched the query and these are results for a corrected spelling of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / hits / items / properties / section / description
      Previous value: -"The documentation section, on a doc hit; null on a component hit."New value: +"On a doc hit, the section key — \"installation\" — to pass to get_doc_page with componentSlug; null on a component hit."
    • addedOutput schema / properties / hits / items / properties / sectionLabel
      Added value: +{
+  "description": "On a doc hit, the section as the site titles it — \"Installation\"; null on a component hit.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / hits / items / properties / type / enum
      Previous value: -[
-  "component",
-  "doc"
-]New value: +[
+  "component",
+  "doc_page"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "correctedQuery": {
+      "description": "Set only when nothing matched the query and these are results for a corrected spelling of it.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hits": {
+      "items": {
+        "properties": {
+          "componentName": {
+            "type": "string"
+          },
+          "componentSlug": {
+            "description": "Pass to get_component or get_doc_page.",
+            "type": "string"
+          },
+          "section": {
+            "description": "The documentation section, on a doc hit; null on a component hit.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "snippet": {
+            "description": "The matching text, with the site's highlight markup stripped.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "description": "A control, or a page of its documentation.",
+            "enum": [
+              "component",
+              "doc"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "description": "Absolute URL of the page, for citing.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "title",
+          "componentSlug",
+          "componentName",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "description": "The query as it was searched.",
+      "type": "string"
+    },
+    "total": {
+      "description": "How many results matched, which may be more than were returned.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "query",
+    "total",
+    "hits"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description adds substantial behavioral context beyond that: it returns both control and documentation hits with snippets and URLs, treats no-match as an empty result (not an error), and discloses that misspellings may yield corrected results that are labeled. This is valuable context that the annotations do not cover.

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 concise yet information-dense, front-loading the core purpose, then usage guidance, then return details and edge cases. Every sentence adds value; there is no redundant or vague wording.

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 search tool with an output schema, the description covers essential context: scope, ranking, return content (snippets and URLs), and unusual behaviors (empty results, misspelling). The presence of an output schema covers return structure, and the description fills in the behavioral gaps, making it complete for an agent to call correctly.

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 description coverage is 100%, so the schema already documents both parameters (query and limit) with clear descriptions. The tool description does not add additional parameter-level semantics beyond what the schema provides, so a 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 clearly states the tool does a full-text search across every published PCF control and its documentation, ranked by relevance. It names specific sibling tools and the conditions under which they should be used instead, making the purpose unambiguous and well-differentiated.

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?

The description explicitly says when to use this tool ('when you know what a control should do but not what it is called') and provides direct alternatives: list_components for filtering by category/tag/author/type, and get_component when you have a slug. It also notes edge-case behavior (empty result vs. error, misspelling correction) which guides expectations.

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

All PCFHub toolsInspect
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