Skip to main content
Glama

Create API token

gameye_create_token

Creates a Gameye API token and writes it to an absolute file path with restricted permissions, supporting scopes, expiry, and dry-run previews.

Instructions

Admin tool. Create a Gameye API token and write it to a file; the token value is never returned. outputPath must be an absolute path outside any git working tree; an existing file is refused unless overwrite=true, and symlinks are always refused. The file is created with 0600 permissions. expires_after defaults to 24h. Requested scopes must be a subset of this server's token scopes (webhook:github is the one exception). Needs the token:write scope. Pass dryRun=true to preview the request. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

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>",
      "scopes": "<scopes>",
      "outputPath": "<outputPath>"
    },
    "name": "gameye_create_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesToken name
dryRunNoCheck outputPath and return the request that would be sent; create nothing
scopesYesScopes for the new token, e.g. ['session:read']
overwriteNoReplace an existing regular file at outputPath
outputPathYesAbsolute path of the file to write the token to
expires_afterNoLifetime such as '1h' or '2h30m' (units m and h). Defaults to 24h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.6/5.0
Behavior5/5

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

Adds rich context beyond the annotations: token value is never returned, file written with 0600 permissions, absolute path required and outside any git working tree, symlinks always refused, existing file refused unless overwrite=true, and the no-token fallback returns setup steps without sending anything. These are precisely the side-effect and safety details an agent needs for a file-writing mutation.

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?

Dense and front-loaded with no filler sentences; each clause carries a constraint the agent cannot get elsewhere. The single run-on paragraph slightly hurts scanability, so it is not a 5.

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?

There is no output schema, but the description covers returns adequately by stating the token value is never returned and describing what happens on a missing API token. For a 6-parameter mutation with real side effects, nothing an agent needs to invoke it 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?

Schema coverage is 100%, so the baseline is 3, and the description goes further by explaining overwrite semantics, the absolute-path/git-worktree constraint, the dryRun preview behavior, the expires_after 24h default, and the scope-subset rule with the webhook:github exception.

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+resource ('Create a Gameye API token') plus the key output behavior ('write it to a file; the token value is never returned'). This distinguishes it from gameplay siblings like gameye_launch_session or gameye_context at a glance.

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 strong conditional guidance: dryRun=true to preview, requires token:write scope, requires GAMEYE_API_TOKEN, and explains the degraded behavior when no token is configured. It does not name alternative tools or explicitly say when not to use this one, which keeps it short of a 5.

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