Skip to main content
Glama

PCFHub

by io.github.pcfhub
OverviewDiscussionsAdmin

List recent releases

list_releases
Read-onlyIdempotent

The most recent releases across every control on PCFHub, newest first: which control, which version, whether it is a prerelease, and when it shipped. Use it for what has changed hub-wide; for one control's own history call get_component with include_versions instead. Bounded by limit, at most 50, and not paged — there is no cursor, so it cannot walk back beyond the newest 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many releases. Defaults to 20.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
releasesYesNewest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "releases": {
+      "description": "Newest first.",
+      "items": {
+        "properties": {
+          "componentName": {
+            "type": "string"
+          },
+          "componentSlug": {
+            "description": "Pass to get_component.",
+            "type": "string"
+          },
+          "isPrerelease": {
+            "type": "boolean"
+          },
+          "releasedAt": {
+            "description": "ISO 8601, or null where the release carries no date.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "Absolute URL of the release.",
+            "type": "string"
+          },
+          "version": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "componentSlug",
+          "componentName",
+          "version",
+          "isPrerelease",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "releases"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds key behavioral facts: it is not paged, has no cursor, and cannot retrieve more than the newest 50. This is valuable context that would otherwise be unknown.

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?

Two sentences, front-loaded with purpose, followed by usage guidance and limitation. Every clause earns its place with no redundancy or fluff.

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?

With an output schema present, the description explains the returned fields, the ordering, the limit behavior, and the alternative tool. Nothing an agent needs to call it correctly 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% and the limit parameter is fully described with min, max, and default. The description only repeats the bound ('at most 50') and does not add new semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 states the exact verb (list) and resource (recent releases across every control on PCFHub), specifies ordering (newest first) and the fields returned. It also distinguishes itself from the sibling tool get_component, making its purpose unambiguous.

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?

Explicitly states when to use it ('what has changed hub-wide') and directs to get_component with include_versions for a single control's history. Also discloses the non-paged, bounded nature, preventing misuse.

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