Skip to main content
Glama
Sign In
quick-game

quick-game

by danilo-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Gerar backlog

gerar_backlog

Generate a milestone-organized BACKLOG.md task list from a game design for the specified game.

Instructions

Transforma o design em uma lista de tarefas (BACKLOG.md) organizada por marcos.

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": {
      "jogo": "<jogo>"
    },
    "name": "gerar_backlog"
  }
}

Input Schema

NameRequiredDescriptionDefault
jogoYesNome ou identificador (slug) do jogo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses little. It implies a file is written (BACKLOG.md) but doesn't say whether an existing backlog is overwritten, whether it is destructive, what permissions or prior state are required, or what happens if no design exists — significant gaps for a generation/write tool.

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?

A single sentence with zero filler, front-loading the transformation and naming the output artifact. Nothing repeats the title verbatim without adding information.

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 one-parameter tool with no output schema, the description covers the core action and the artifact produced, which is the minimum viable set. It nonetheless omits the prerequisite state, overwrite behavior, and sibling routing that an agent needs to call it safely.

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 100% with a single 'jogo' parameter whose description ('Nome ou identificador (slug) do jogo') is already documented in the schema. The description adds implicit meaning by naming 'o design' as the source material, but gives no parameter-level syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Transforma o design em uma lista de tarefas (BACKLOG.md)') plus the organizing principle ('por marcos'), which is concrete enough to act on. It does not, however, differentiate itself from sibling generation tools like gerar_gdd or gerar_prototipo, so an agent must infer which generator applies.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives. The description never says the design/GDD must already exist, nor where this fits relative to guia_etapa, gerar_gdd, or checar_escopo.

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

Deploy Server

Other Tools