Skip to main content
Glama

get_publish_guide

Read-onlyIdempotent

The rules a browser game must follow to run on YouGame (build layout, paths, limits, the runtime sandbox, desktop/mobile reserved button areas, what usually breaks and how to fix it) plus how to verify and upload. Read this first when making a game YouGame-ready. The whole guide is long: pass topic (a heading such as "Desktop builds" or "Publishing from a coding agent") for just that part; an unknown topic 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_publish_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional: one heading of the guide, or words from it. Omit for the whole guide.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, so the safety profile is covered. The description adds genuinely new behavioral detail: the full guide is long, topic narrows the response to one heading, and an unknown topic returns the heading list instead of failing — useful failure-mode disclosure that the annotations cannot express.

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?

The leading clause states what the guide contains and the second sentence states how to read it selectively — front-loaded and purposeful. The parenthetical content list is dense but each item describes real guide coverage, so little is wasted.

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

Completeness4/5

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

For a zero-required-param, no-output-schema read tool with full annotation coverage, the description covers content scope, filtering behavior, and the unknown-topic response. Only a hand-off to publish_game after the guide is followed would make it fully complete.

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

Parameters3/5

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

Schema coverage is 100% and the parameter already documents itself as an optional heading or words from it. The description adds concrete examples of valid headings ("Desktop builds", "Publishing from a coding agent") and the unknown-topic fallback, which is modest added meaning, so a baseline 3 is defensible.

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?

States a specific resource (the YouGame publishing guide) and enumerates its coverage: build layout, paths, limits, runtime sandbox, reserved button areas, failure modes, and verify/upload steps. That is far more concrete than a name restatement, though it never explicitly contrasts itself with get_sdk_reference or publish_game, so sibling differentiation is only implicit.

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?

"Read this first when making a game YouGame-ready" gives a clear trigger condition, and the topic-parameter sentence clarifies the narrow vs. broad read path. It stops short of naming alternatives (e.g., use publish_game once the guide is satisfied), so the routing is contextual rather than explicit.

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