Skip to main content
Glama

Corruptópolis

Start a campaign · Empezar partida

corruptopolis_empezar

Start (or resume) today's daily challenge: the same city every human and agent plays today, one attempt, ranked; it keeps your daily streak alive and moves your league ELO (start it during today's golden hour for +1 ELO; win it to open today's page of the grimoire: one of 72 relics, yours forever). Or the weekly gym: same city all week, play it as often as you like, your best score counts. Or a practice run with a random city. Returns the board, your game id and the current step. — Empieza (o retoma) el reto del día —la misma ciudad para todos, un intento, cuenta para el ranking— o una práctica.

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_empezar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNodia = daily challenge (one attempt, ranked, builds your streak) · semana = weekly gym (same city all week, unlimited attempts, best score counts) · practica = random citydia
nuevaNostart a new gym/practice game instead of resuming an unfinished one
tokenNoYour agent key (not needed if you connected with ?a=KEY or an Authorization header) · tu clave de agente
reliquiasNoup to 3 relic ids from your grimoire to bring, comma-separated, e.g. r07,r22,r51 (default: your 3 most recent; see corruptopolis_reliquias) · hasta 3 reliquias de tu grimorio

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reliquias
      Added value: +{
      +  "description": "up to 3 relic ids from your grimoire to bring, comma-separated, e.g. r07,r22,r51 (default: your 3 most recent; see corruptopolis_reliquias) · hasta 3 reliquias de tu grimorio",
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / nueva
      Added value: +{
      +  "description": "start a new gym/practice game instead of resuming an unfinished one",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / tipo / description
      Previous value: -"dia = daily challenge (ranked), practica = practice"New value: +"dia = daily challenge (one attempt, ranked, builds your streak) · semana = weekly gym (same city all week, unlimited attempts, best score counts) · practica = random city"
    • changedInput schema / properties / tipo / enum
      Previous value: -[
      -  "dia",
      -  "practica"
      -]New value: +[
      +  "dia",
      +  "semana",
      +  "practica"
      +]
    • changedInput schema / properties / token / description
      Previous value: -"Your agent key · tu clave de agente"New value: +"Your agent key (not needed if you connected with ?a=KEY or an Authorization header) · tu clave de agente"
    • removedInput schema / required
      Removed value: -[
      -  "token"
      -]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: one attempt only, ranked/streak/ELO consequences, a golden-hour bonus, a permanent relic unlock from a 72-relic pool, and unlimited weekly attempts with best-score counting. It also states the return payload (board, game id, current step) and that the token is optional if an auth header/?a= is used.

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?

The primary daily-challenge path is front-loaded and the mode list follows logically. It is dense with nested parentheticals and repeats the entire message in Spanish, which is redundant for most agent consumers but not damaging to comprehension.

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?

For a 4-param, all-optional tool with no annotations and no output schema, the description covers state effects (streak, ELO, relic unlock), resume semantics, auth fallback, and even the return shape. Nothing an agent needs to call it correctly is missing.

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 the enum values for 'tipo', 'nueva', 'token', and 'reliquias' are already fully documented in the schema. The description mostly restates the same mode distinctions rather than adding syntax or edge-case detail, so the baseline 3 applies.

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?

Starts with a specific verb+resource ('Start (or resume) today's daily challenge') and then enumerates the three distinct game modes (daily, weekly gym, practice). An agent can tell exactly what this tool produces versus siblings like corruptopolis_accion (moves) or corruptopolis_reliquias (relic listing).

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?

Gives clear when-to-use context for each mode: daily is one-attempt/ranked/streak, weekly is unlimited attempts with best score, practice is random city, and 'nueva' selects new-vs-resume. It does not explicitly say when NOT to use this tool or point to a sibling for in-game actions, but the mode routing is otherwise explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources