Skip to main content
Glama
Sign In
quick-game

quick-game

by danilo-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Salvar etapa

salvar_etapa

Saves and merges a user's decisions for a game-creation stage. Set concluir=true after confirmation; the stage closes only when required fields are complete.

Instructions

Registra as decisões do usuário em uma etapa (mescla com o que já existe). Use concluir=true depois que o usuário confirmar o resumo; a etapa só fecha se os campos obrigatórios estiverem preenchidos.

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>",
      "etapa": "<etapa>",
      "dados": "<dados>"
    },
    "name": "salvar_etapa"
  }
}

Input Schema

NameRequiredDescriptionDefault
jogoYesNome ou identificador (slug) do jogo
dadosYesCampos da etapa (ids de guia_etapa). Campos extras também são aceitos.
etapaYes
concluirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real behavioral context: it merges rather than replaces, and the step only closes when required fields are filled. It does not disclose permissions, validation-failure behavior, or what happens on partial failure, leaving meaningful gaps for a mutation tool.

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?

Two sentences, no filler, with the merge behavior and the concluir condition front-loaded. Efficient and readable, though it could omit the trailing clause without losing much.

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?

No output schema and no annotations, so the description must cover behavior, parameters, and results. It handles merge semantics and the completion gate but omits error handling, return shape, and the meaning of the 'etapa' identifier, which is thin for a 4-param mutation with nested objects.

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 50%; 'etapa' and 'concluir' have no schema descriptions. The description compensates for 'concluir' by explaining its confirmation-then-close semantics and touches the merge behavior of 'dados', but says nothing about 'jogo' or 'etapa', so it only partially fills the gap.

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: 'Registra as decisões do usuário em uma etapa', with the parenthetical '(mescla com o que já existe)' clarifying the write semantics. It is distinguishable from siblings like anotar_decisao and guia_etapa, though it does not name them explicitly.

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

Usage Guidelines3/5

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

Gives one explicit usage condition: 'Use concluir=true depois que o usuário confirmar o resumo'. However it says nothing about when to prefer this tool over anotar_decisao, guia_etapa, or listar_etapas, so the alternative-selection guidance is implied at best.

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