Skip to main content
Glama
Sign In

Corruptópolis

by io.github.Portuno
OverviewDiscussionsAdmin

The 72 relics of the grimoire · Las 72 reliquias

corruptopolis_reliquias

The 72 relics of Galturn's grimoire: each one an angel, a demon and one of Wukong's transformations, with real rule changes (lower quotas, hate shields, extra memes, veto immunity…). Win the daily challenge to open the page of the day forever; find more as rewards inside runs (they stay if you finish a daily with ELO 12+); bring up to 3 into any run. With your key it marks the ones in your grimoire. — Las 72 reliquias: catálogo y tu grimorio.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "corruptopolis_reliquias"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNooptional: one relic, e.g. r09
tokenNooptional: your key, to mark your grimoire (not needed if connected with ?a=KEY)
heliceNooptional: filter by thread

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it never explicitly states this is a read-only lookup, nor what the response looks like or whether omitting id returns all 72 relics. The one behavioral note — 'with your key it marks the ones in your grimoire' — duplicates the token parameter's own schema description rather than adding new context.

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

Conciseness3/5

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

A single long semicolon-chained sentence front-loads flavor ('Galturn's grimoire') rather than the operation, and the trailing Spanish sentence is a near-duplicate of the English. Not bloated in absolute length, but the space is spent on setting and repetition instead of operational facts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-optional-parameter read-only lookup with no annotations and no output schema, the description should clarify the result shape (single relic vs. full catalog, what fields each relic exposes). It covers the thematic domain well but leaves the agent guessing about the returned payload.

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%, so baseline is 3. The description loosely maps its framing (angel/demon/wukong threads, grimoire marking by key) onto helice and token, but adds no filtering syntax, matching behavior, or detail for id beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause plus the closing 'catálogo y tu grimorio' make it inferable that this is a relic catalog/lookup tool, and the angel/demon/wukong framing matches the helice enum. But it never states a verb or what an invocation returns (a list? a single relic's effects?), so the purpose is expressed through lore rather than a clean verb+resource statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The middle clauses ('Win the daily challenge to open the page of the day forever', 'find more as rewards inside runs', 'bring up to 3 into any run') describe in-game acquisition mechanics, not when an agent should call this tool. No condition, prerequisite, or comparison to siblings like corruptopolis_informe or corruptopolis_perfil is given.

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

All Corruptópolis 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