Skip to main content
Glama

List the bundled Gameye skills

gameye_list_skills
Read-onlyIdempotent

Lists the Gameye agent skills bundled with this server, including names, descriptions, versions, files, and pack version. Use it to inspect available skills offline without a Gameye account.

Instructions

Works without a Gameye account or token. List the Gameye agent skills bundled with this server: each skill's name, description, version and files, and the bundled pack version. Works offline. Read one with gameye_get_skill. If an installed copy of the Gameye skills is newer, it wins.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gameye_list_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.6/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 profile is covered. The description adds genuinely new behavior: it works offline and without credentials, and it discloses a precedence rule ("If an installed copy of the Gameye skills is newer, it wins") that affects how an agent should interpret results. It does not discuss result ordering or size, which keeps it just short of a 5.

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?

Roughly three short sentences that are front-loaded with the credential-free property, which is what an agent needs before deciding to call. Minor redundancy between the opening "Works without a Gameye account or token" and the later "Works offline." keeps it from being maximally tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema and strong annotations, the description fills exactly the remaining gaps: what the result contains, that no auth is needed, and the freshness precedence rule. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly spends no words on arguments and instead covers scope and return content.

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?

The description uses a specific verb and resource ("List the Gameye agent skills bundled with this server") and enumerates the returned fields (name, description, version, files, pack version). It is immediately distinguishable from the sibling gameye_get_skill, which reads a single skill.

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

Usage Guidelines5/5

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

It names the alternative explicitly ("Read one with gameye_get_skill") and states the branching condition: list here, read individual skills there. It also removes the usual adoption blocker by clarifying no account or token is required, so an agent knows it can call this first with no prerequisites.

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