Skip to main content
Glama

Read a bundled Gameye skill

gameye_get_skill
Read-onlyIdempotent

Read a bundled Gameye agent skill file offline without an account or token; retrieve SKILL.md or reference docs to access packaged skill guidance.

Instructions

Works without a Gameye account or token. Read a Gameye agent skill bundled with this server: its SKILL.md, or one of its reference files. Works offline and serves only the bundled copy (list names and files with gameye_list_skills). If an installed copy of the Gameye skills is newer, it wins.

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

Input Schema

NameRequiredDescriptionDefault
fileNoFile inside the skill, e.g. references/routing.md. Defaults to SKILL.md
nameYesSkill name, e.g. gameye or gameye-containerize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low. The description still adds meaningful behavior: it works without credentials or network, serves only the bundled copy rather than any installed one, and defers to a newer installed copy — details an agent could not infer from annotations.

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?

Three short sentences, front-loaded with the most important constraint (no account or token). Every sentence carries information — offline behavior, scope limits, precedence — with no filler or repetition.

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 two-parameter read tool with annotations and no output schema, the description supplies what is missing: credential-free access, offline operation, bundled-only scope, and conflict resolution with installed copies. The only unchecked box is what the returned content looks like, which is largely self-evident for reading a file.

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% and both parameters already carry examples in their descriptions, so the schema does the heavy lifting. The description reinforces the file-among-references concept and tells the agent where to find valid names, but adds little per-parameter syntax or default detail beyond what is structured.

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?

States a specific verb and resource ("Read a Gameye agent skill bundled with this server") and scopes it precisely to SKILL.md or a reference file. It also names the sibling that enumerates skills (gameye_list_skills), so an agent can distinguish read-one from list-all without opening schemas.

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 context for use: no account or token needed, works offline, and points to gameye_list_skills for discovering valid names and files. It also states a precedence rule against newer installed copies. It stops short of an explicit when-not-to-use case, but the routing context is solid.

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