Skip to main content
Glama
Sign In

ChangeGamer

by ai.changegamer
OverviewDiscussionsAdmin

Get free corpus

get_corpus
Read-onlyIdempotent

Return the entire free corpus as one document (every free resource title, description, canonical URL, and full Markdown body) — the same content as /llms-full.txt. Premium resources appear as a stub with a purchase link, not their body. Use this to ingest everything in a single call; the response is large. Optional category returns only that category's resources (smaller result). Size without category: about 890 KB.

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly resources in this category (case-insensitive): Guide, Policy, Reference, Meta. Omit for the whole corpus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / category / maxLength
      Added value: +200
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / category
      Added value: +{
+  "description": "Only resources in this category (case-insensitive): Guide, Policy, Reference, Meta. Omit for the whole corpus.",
+  "type": "string"
+}
  3. 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 closed-world, so the safety profile is covered. The description adds genuinely new behavioral context on top: premium entries come back as a purchase-link stub rather than a body, the response is large, and it is roughly 890 KB uncategorized.

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?

One dense paragraph that front-loads what is returned, then the premium-stub caveat, then usage, then size. Efficient overall, though "the response is large" and "about 890 KB" convey the same warning twice.

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?

With no output schema, the description carries the return-shape burden and does it: it enumerates the fields returned, explains how premium entries differ, and quantifies payload size so the agent can anticipate token cost. The only gap is the missing contrast with get_full_corpus.

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 the schema already enumerates the four category values (Guide, Policy, Reference, Meta) and the omit-for-whole-corpus behavior. The description only repeats the intent ("only that category's resources, smaller result") without adding syntax or edge-case meaning, so baseline 3 applies.

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 and resource: returns the entire free corpus as one document, with a concrete field list (title, description, canonical URL, Markdown body) and an explicit stub policy for premium resources. It does not, however, name or distinguish itself from the sibling get_full_corpus, leaving the agent to infer the difference between 'free corpus' and 'full corpus'.

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 ingest everything in a single call" gives a clear selecting condition (bulk ingestion vs. per-item access via get_article/search), and the optional category is framed as the way to get a smaller result. There is no explicit when-not or named alternative, so it stops short of a 5.

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