Skip to main content
Glama
Sign In

changegamer

by io.github.beneb89
OverviewDiscussionsAdmin

Search resources

search_resources
Read-onlyIdempotent

Search the ChangeGamer corpus by keyword. Every word must match the title, tags, category, description or (as a last resort) the body; results rank title > tags > category > description > body, the same order as the site search. Returns metadata plus HTML/Markdown/JSON URLs (no body content). Use this to find resources before fetching them with get_resource.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 10).
queryYesSearch keywords, e.g. "retrieval augmented generation" or "mcp auth"

Output Schema

NameRequiredDescriptionDefault
countYes
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / query / maxLength
      Added value: +500
    • 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": {
+          "markdown": {
+            "type": "string"
+          },
+          "premium": {
+            "type": "boolean"
+          },
+          "relevance": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "premium",
+          "relevance",
+          "markdown"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing the AND-matching rule (every word must match), the field-priority ranking order, and the fact that results contain only metadata and HTML/Markdown/JSON URLs with no body content.

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 sentences, no filler, and the matching/ranking rules are front-loaded before the return-format and routing guidance. Every clause carries information an agent would otherwise have to guess.

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?

Covers search semantics, ranking, failure mode of body-only matches, return payload shape, and the natural next tool. With annotations and an output schema already present, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: it explains that all query terms must match and where they are matched, which is more than the schema's simple example string conveys. The limit parameter is left entirely to the schema.

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?

States a specific verb (search) and resource (ChangeGamer corpus) plus the exact matching rules across title, tags, category, description and body. It clearly separates itself from get_resource by describing itself as the discovery step that returns metadata/URLs rather than content.

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?

"Use this to find resources before fetching them with get_resource" gives an explicit when-to-use and names the follow-up tool. It does not, however, distinguish itself from the sibling tool named `search`, leaving an ambiguity an agent must resolve on its own.

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