Playgama MCP - Publish & Manage HTML5 Games

Create a leaderboard

create_leaderboard

Destructive

Add a leaderboard to a game. id is its Bridge SDK tag: unique within the game and not changeable later. Check list_leaderboards for tags already taken. Deleting a leaderboard is not available.

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": {
      "applicationId": "<applicationId>",
      "id": "<id>",
      "name": "<name>",
      "type": "<type>"
    },
    "name": "create_leaderboard"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The tag the game passes to the Playgama Bridge SDK, e.g. top_players. Unique within the game
`name`	Yes	Human-readable name of the leaderboard, as the console shows it
`type`	Yes	What a score is: `numeric` for points, `time` for a duration. The ranking direction is `scoreOrder`.
`decimals`	No	Number of decimal places for scores, 0 to 32767. Default 0. Scores are stored as whole numbers — a fractional score the game submits is rounded — so this does not make fractional scores possible.
`scoreOrder`	No	`desc` ranks the highest score first, `asc` the lowest — e.g. the fastest time. Default desc.
`applicationId`	Yes	Game id from list_applications

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / applicationId / description

Previous value: -"Application (game) id, as returned by list_applications"New value: +"Game id from list_applications"

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / name / description

Previous value: -"Human-readable name of the leaderboard, as the cabinet shows it"New value: +"Human-readable name of the leaderboard, as the console shows it"

Changed7 schema fields changedSep 11, 2026

addedInput schema / properties / decimals / description

Added value: +"Number of decimal places for scores, 0 to 32767. Default 0. Scores are stored as whole numbers — a fractional score the game submits is rounded — so this does not make fractional scores possible."

changedInput schema / properties / decimals / maximum

Previous value: -9007199254740991New value: +32767

changedInput schema / properties / decimals / minimum
```
Previous value: --9007199254740991New value: +0
```

changedInput schema / properties / id / description

Previous value: -"Leaderboard tag, e.g. top_players"New value: +"The tag the game passes to the Playgama Bridge SDK, e.g. top_players. Unique within the game"

addedInput schema / properties / name / description

Added value: +"Human-readable name of the leaderboard, as the cabinet shows it"

addedInput schema / properties / scoreOrder / description

Added value: +"`desc` ranks the highest score first, `asc` the lowest — e.g. the fastest time. Default desc."

addedInput schema / properties / type / description

Added value: +"What a score is: `numeric` for points, `time` for a duration. The ranking direction is `scoreOrder`."

First observedSep 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, the description discloses two important lifecycle constraints: the id cannot be changed later and deleting a leaderboard is unavailable. This usefully reinforces the non-idempotent, destructive annotation profile without contradicting it. It does not cover permissions or duplicate-tag failure behavior, but the critical irreversibility is disclosed.

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

Conciseness5/5

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

Three tightly written sentences front-load the action, then the key id constraint, then the pre-check and lifecycle limitation. Every sentence adds useful information with no filler.

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 six-parameter creation tool with complete schema descriptions and safety annotations, the description covers the most important non-obvious constraints: tag uniqueness, immutability, and permanent deletion unavailability. It stops short of explaining the return value or permission requirements, but the essential call-time context is present.

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%, so the schema already defines all six parameters and their formats. The description adds only one meaningful detail beyond the schema: that id is immutable after creation. That is valuable but not enough to compensate broadly across the other parameters.

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?

The description states a specific verb and resource: 'Add a leaderboard to a game.' It clearly distinguishes creation from the sibling list_leaderboards by directing tag checks there, and from update_leaderboard by framing the action as adding a new leaderboard.

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?

It gives a concrete prerequisite: check list_leaderboards for tags already taken. It does not explicitly state when to use update_leaderboard instead, but the create-versus-list guidance is clear and actionable.

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

All Playgama MCP - Publish & Manage HTML5 Games tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?