Skip to main content
Glama

Corruptópolis

Make a move · Hacer una jugada

corruptopolis_accion

One move per call. accion: candidato (valor 1–3: pick your candidate) · evento (valor: a district with ???) · respuesta (si|no) · simular (try a play without launching it) · jugar (place memes and launch the month; valor "CARD:DISTRICT,…", card = number in your hand, district by name: puerto, cabildo, iglesia, polideportivo, universidad, marina) · cambiar (redraw your hand) · querer (si|no: call or let pass the rival’s declaration of where his counter-meme lands; he may be bluffing) · cantar (valor: a district: announce where you will play; if he believes you he moves his counter-meme there, and if you then don’t play there the Church charges +1 hate) · premio (1–3 or saltar) · estado (just look). Always send the current paso: a stale step is ignored, so retries are safe. Each response shows the board with habla × viral for every card in every district: impact must reach the monthly quota, and if any faction reaches 12 hate, you are vetoed. — Una acción por llamada; manda siempre el paso actual.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "partida": "<partida>",
      "accion": "<accion>"
    },
    "name": "corruptopolis_accion"
  }
}

Input Schema

NameRequiredDescriptionDefault
pasoNocurrent step · paso actual
tokenNo
valorNo
accionYes
partidaYesgame id · id de partida

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / accion / enum
      Previous value: -[
      -  "estado",
      -  "candidato",
      -  "evento",
      -  "respuesta",
      -  "simular",
      -  "jugar",
      -  "cambiar",
      -  "premio"
      -]New value: +[
      +  "estado",
      +  "candidato",
      +  "evento",
      +  "respuesta",
      +  "simular",
      +  "jugar",
      +  "cambiar",
      +  "querer",
      +  "cantar",
      +  "premio"
      +]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "token",
      -  "partida",
      -  "accion"
      -]New value: +[
      +  "partida",
      +  "accion"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses idempotency semantics (stale paso ignored, retries safe), a concrete penalty ('the Church charges +1 hate' for a broken cantar), a loss condition ('if any faction reaches 12 hate, you are vetoed'), and that the rival 'may be bluffing'. Gaps remain around the unexplained token parameter and error behaviour on an invalid accion/valor.

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?

It is front-loaded with the key constraint, but the body is a single run-on paragraph of mid-dot-separated clauses, so the ten action semantics are hard to scan and easy to mis-parse. The trailing bilingual restatement ('— Una acción por llamada; manda siempre el paso actual.') duplicates content already stated and does not earn its place.

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?

For a ten-action game tool with no output schema and no annotations, the description covers the domain well: the response shape is previewed ('shows the board with habla × viral for every card in every district'), and the win/veto conditions are stated. The remaining holes — token handling and what an invalid or out-of-turn action returns — are real but secondary for correct invocation.

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 only 40%, but the description compensates heavily for valor, giving per-action formats ('CARD:DISTRICT,…', '1–3 or saltar', 'si|no') and even enumerating the six district names, plus the meaning of paso. However, token is documented nowhere, and partida is only covered by the schema's own 'game id' description, so the low-coverage baseline is not fully offset.

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?

The opening 'One move per call' plus the accion enum spelled out inline ('simular (try a play without launching it)', 'jugar (place memes and launch the month)') makes it unambiguous that this is the single gameplay-mutation endpoint. It does not name any sibling tool, so an agent must infer from sibling names alone that profile/ranking/report live elsewhere.

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?

Each accion value carries its own when-to-use gloss, including the distinction between 'simular' (dry run) and 'jugar' (commit), which is exactly the guidance an agent needs to avoid an accidental launch. It also gives the operational rule 'Always send the current paso: a stale step is ignored, so retries are safe.' What is missing is any explicit routing to alternatives (e.g. when to call corruptopolis_informe instead of accion=estado).

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