Skip to main content
Glama
Sign In
quick-game

quick-game

by danilo-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ler skill

ler_skill

Fetches the complete content of a skill file (SKILL.md) or reads a specified auxiliary reference file to support game creation workflows.

Instructions

Carrega o conteúdo completo de uma skill (SKILL.md). Com 'referencia', lê um arquivo auxiliar da skill.

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": {
      "nome": "<nome>"
    },
    "name": "ler_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeYes
referenciaNoCaminho relativo de um arquivo listado em 'referencias'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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. It explains that a plain call returns full content and a 'referencia' call returns an auxiliary file, but says nothing about permissions, error behavior when a skill/file is missing, or return format.

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 tight sentences with the primary action front-loaded and the optional parameter noted second. No wasted words.

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 simple two-parameter read tool with no output schema, the description roughly covers the return intent ('conteúdo completo'). However, with zero annotation coverage it should say more about permissions, error cases, and the distinction between the full-skill and auxiliary-file reads.

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%: 'referencia' is documented in the schema while 'nome' is not. The description adds meaning by clarifying that 'referencia' reads an auxiliary file of the skill, but it never explains 'nome' beyond the obvious implication that it names the skill.

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 description states a specific verb+resource: it loads the complete content of a skill (SKILL.md) and, optionally, reads an auxiliary file. This clearly differentiates it from siblings like listar_skills and recarregar_skills, though it never names 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 Guidelines2/5

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

There is no explicit when-to-use guidance or routing versus alternatives such as listar_skills or recarregar_skills. Usage is only implied by the verb 'carrega'.

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