ChangeGamer

List resources

list_resources

Read-onlyIdempotent

List all ChangeGamer resources with metadata and absolute URLs. Returns slug, title, description, category, tags, updated date, premium flag, and HTML/Markdown/JSON variant URLs. No body content. Optional category and premium filters narrow the list; without them every resource is returned.

Input Schema

Name	Required	Description	Default
`premium`	No	true = only premium resources, false = only free ones.
`category`	No	Only resources in this category (case-insensitive): Guide, Policy, Reference, Meta.

Output Schema

Name	Required	Description	Default
`resources`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / category

Added value: +{
+  "description": "Only resources in this category (case-insensitive): Guide, Policy, Reference, Meta.",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / premium

Added value: +{
+  "description": "true = only premium resources, false = only free ones.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "resources": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "markdown": {
+            "type": "string"
+          },
+          "premium": {
+            "type": "boolean"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "category",
+          "premium",
+          "markdown"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "resources"
+  ],
+  "type": "object"
+}

First observedJun 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context: full field inventory, absolute URLs, URL variants per format, and the explicit "No body content" limitation. It stops short of noting result size or pagination when no filter is applied.

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?

Three tight sentences: identity, return shape, then filter behavior. Front-loaded with the core operation, zero filler, and the "No body content" caveat sits before the parameter note where it matters most.

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?

An output schema exists so return values needn't be spelled out, and annotations cover the safety profile. A 2-param read-only list tool is well served here; the only gap is no guidance on unfiltered result volume, which is a plausible concern given the description promises every resource when unfiltered.

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% and both params carry their own enum-like value lists, so the baseline is 3. The description contributes only the default behavior ("without them every resource is returned"), which is a marginal addition over the schema's own definitions.

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?

Specific verb+resource ("List all ChangeGamer resources") plus an explicit inventory of returned fields and the boundary "No body content." It does not name the sibling it is distinguished from (search_resources, get_resource), so the agent must infer the split, but the purpose itself is unambiguous.

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?

"Optional `category` and `premium` filters narrow the list; without them every resource is returned" covers the filtering decision but says nothing about when to prefer this over search_resources or get_resource, or when not to call it (e.g. large unfiltered result sets). Usage is implied, not directed.

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

All ChangeGamer 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?