Skip to main content
Glama

my_games

Read-onlyIdempotent

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). The games the API key's creator has published on YouGame: id (what crowd coding and other id-keyed calls take), slug, URL, title, version, plays, SDK features. Needs the creator's API key.

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": "my_games"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / api_key
      Removed value: -{
      -  "description": "Only when the key could not be set as the Authorization header of the MCP connection: the creator's API key (yg_…). Prefer the header (or the YOUGAME_API_KEY environment variable): a key passed here ends up in the agent's transcript and tool logs.",
      -  "type": "string"
      -}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: authentication is mandatory and can be satisfied via OAuth connection or an Authorization: Bearer API key. It also discloses the result shape (the field list), which annotations cannot convey. It stops short of noting scoping limits such as pagination or whether unpublished/draft games are excluded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading the auth requirement is sensible, but the requirement is stated twice ('Needs sign-in...' and the trailing 'Needs the creator's API key'), which is redundant in a three-sentence description. The middle sentence is dense but well-formed; trimming the duplicated auth note would make this 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 and no output schema, the description carries the burden of explaining what comes back, and it does so by enumerating the returned fields. Combined with the auth prerequisites and the note about id reuse, an agent has everything needed to call this correctly on the first attempt.

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 the baseline is 4 and there is no parameter meaning for the description to add. The one relevant input-side fact — that a creator API key must be supplied — is stated, which is the only input constraint that exists.

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 names a specific resource and scope: the games published on YouGame by the API key's creator, plus the fields returned (id, slug, URL, title, version, plays, SDK features). It is clearly a 'list my own games' read, distinguishable from setup/mutation siblings like publish_game or add_version, though it never states the verb directly.

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?

Usage is implied rather than stated: the parenthetical that id is 'what crowd coding and other id-keyed calls take' hints this tool is the entry point for obtaining ids needed elsewhere. There is no explicit when-to-use/when-not-to-use guidance and no named alternative, so the agent must infer placement in a workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources