Skip to main content
Glama

get_sdk_reference

Read-onlyIdempotent

The complete YouGame SDK reference: desktop/mobile button positions and reserved screen areas, touch controls, leaderboards (gameOver / submitScore), beat-my-score links, saves (save / load, kept on the player's account), online multiplayer with matchmaking, friend invites, skill ratings, voice chat between friends that a game with a map can turn into proximity chat (YouGame.voice), persistent worlds (shared state kept between visits; not a game server), replays (YouGame.replay: record the game's state frame by frame, play it back with pause and seek, watch links; input recording for deterministic games). One script tag, no account needed. The whole reference is long: pass section (a heading such as "Multiplayer" or "Native builds") for just that part; an unknown section answers with the list of headings.

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

Input Schema

NameRequiredDescriptionDefault
sectionNoOptional: one heading of the reference, or words from it. Omit for the whole reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section
      Added value: +{
      +  "description": "Optional: one heading of the reference, or words from it. Omit for the whole reference.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description still adds real behavior: the response is large unless scoped, an unknown section returns the list of headings rather than failing, and the reference targets a no-account, one-script-tag setup.

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?

Front-loads the resource, then the scoping rule. The long enumerated topic list is bulky and runs on through nested parentheses, but it does double duty as a table of contents that lets the agent pick a valid section, so most of it earns its place.

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?

For a single optional string parameter with full schema coverage and annotations carrying the safety profile, nothing an agent needs is missing: size expectations, scoping, and unknown-section behavior are all covered, and no output schema exists that the description would need to explain.

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 baseline is 3. The description goes beyond the schema by giving concrete example headings ('Multiplayer', 'Native builds'), explaining the fallback for an unrecognized section, and giving the reason (length) to use the parameter at all.

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 resource ('The complete YouGame SDK reference') and enumerates the domains it covers — input, leaderboards, saves, multiplayer, voice, replays — so an agent knows exactly what retrieval this is and can tell it apart from sibling doc/source tools like get_publish_guide or get_source.

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 operational guidance for the one decision that matters: pass a section heading for a narrower slice, omit it for the whole thing. It also warns the full reference is long, which implicitly steers toward scoping. It does not explicitly compare itself to sibling document tools, so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources