Skip to main content
Glama

GameGene: gene の全体 (all design genes / mechanics)

gamegene_genes
Read-only

Mechanics traced across games: what a genre is built from, ideas to combine. ジャンルを組み立てている仕組み (Gene) を、作品をまたいで全部返す。組み合わせの案を探すときに使う。All design genes GameGene records: each gene is a mechanic traced across the games that carry it (for example a deckbuilder's card draft or a roguelite's meta progression), with its definition and the games' slugs. Use it to see the whole map of mechanics at once, for example when someone asks which mechanics a genre is built from or wants ideas to combine. For one mechanic, gamegene_search with types ["genes"] and then gamegene_claims with geneSlug is lighter. compact: true returns only each gene's slug, names, category and number of games (no definitions or game slugs), much smaller; use it to pick genes, then read them with gamegene_claims. GameGene が記録している設計上の遺伝子 (gene) を全件返す。各 gene には定義文と、その gene を持つ作品の slug が並ぶ。ページングしない — 設計空間の全体を一度に渡すための tool である。

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

Input Schema

NameRequiredDescriptionDefault
compactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioural context beyond them: the tool does not paginate and returns the entire design space in one call, and compact: true shrinks the payload to slug/name/category/game-count. It does not warn about response size limits or latency for the unpaginated full dump, which is the main remaining gap.

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?

The lead sentence is well front-loaded, but the same content is restated three times (English summary, Japanese summary, longer English paragraph, then Japanese again), so a large fraction of the text is duplication rather than added information. The bilingual mirroring may be intentional, yet it makes the definition noticeably longer than the information it carries.

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, so the description must explain return values, and it does: per-gene definition text plus carrying-game slugs, and the reduced field set under compact. Combined with the no-pagination statement and the routing to siblings for single-gene lookups, an agent has everything needed to call this correctly.

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

Parameters5/5

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

Schema coverage is 0% — the single `compact` boolean has no schema description — so the description must carry it, and it does fully: it enumerates exactly which fields compact returns (slug, names, category, number of games) and which it drops (definitions, game slugs), plus the follow-up call needed to read full records.

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: returns all design 'genes' (mechanics traced across games) that GameGene records, each with its definition and the slugs of games that carry it. Concrete examples (deckbuilder card draft, roguelite meta progression) pin down what a gene is, and the description explicitly contrasts itself with the narrower path via gamegene_search + gamegene_claims.

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?

Gives explicit when-to-use conditions: 'when someone asks which mechanics a genre is built from or wants ideas to combine'. It also names the alternative for a single mechanic (gamegene_search with types ["genes"] then gamegene_claims with geneSlug, described as 'lighter'), and prescribes a two-step workflow for compact mode.

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