Skip to main content
Glama
Sign In

changegamer

by io.github.beneb89
OverviewDiscussionsAdmin

Search resources and guides

search
Read-onlyIdempotent

Keyword search across ALL ChangeGamer content (resources and editorial guides), ranked like the site search: every word must match; title hits weigh most, then tags, category, description. Returns ranked rows with type, slug, title, description, premium flag, .md and HTML URLs (no body content). Use get_resource/get_article to fetch winners.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query — one or more keywords; every word must match
typeNoOnly resources or only guides (articles).
limitNoMax results (default 10)

Output Schema

NameRequiredDescriptionDefault
countYes
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / q / description
      Previous value: -"Search query — one or more keywords"New value: +"Search query — one or more keywords; every word must match"
    • addedInput schema / properties / q / maxLength
      Added value: +500
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Only resources or only guides (articles).",
+  "enum": [
+    "resource",
+    "article"
+  ],
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "premium": {
+            "type": "boolean"
+          },
+          "score": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "resource",
+              "article"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "score",
+          "type",
+          "slug",
+          "title",
+          "premium",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral detail: AND-matching semantics, the ranking order (title > tags > category > description), and the fact that bodies are excluded. Missing only edge-case behavior such as empty-result handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with scope, then ranking, then return shape and next step. Dense but nearly every clause carries information; the ranking-weight list is the only part bordering on excess given the output schema.

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, yet the description still names the returned fields and flags that bodies are absent, which is beyond requirement. Combined with matching/ranking semantics and a follow-up route, an agent has everything needed to call it 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 coverage is 100% and each parameter is documented in the schema, so the baseline is 3. The description adds the ranking/matching model, but repeats 'every word must match' which q's schema text already states.

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?

States a specific verb and resource ('Keyword search across ALL ChangeGamer content') and clarifies scope as resources plus editorial guides, which separates it from get_resource/get_article. It does not, however, distinguish itself from the very similar sibling search_resources, leaving the agent to infer which to pick.

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?

Explicitly routes the agent onward: 'Use get_resource/get_article to fetch winners', establishing this as a discovery tool rather than a fetcher. It gives no guidance on when to prefer it over the sibling search_resources or list_resources.

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

All changegamer 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