Skip to main content
Glama
isco-tec
by isco-tec

create_board

Add a leaderboard board to an EXISTING game (by gameId — get it from list_games). This is how you add boards to a game that already exists; bootstrap_leaderboard only works for brand-new games.

Instructions

Add a leaderboard board to an EXISTING game (by gameId — get it from list_games). This is how you add boards to a game that already exists; bootstrap_leaderboard only works for brand-new games. sortDir "desc" = high-scores-win, "asc" = lowest-time-wins. Returns the created board including its id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name of the leaderboard
slugYesURL-safe slug for the board, e.g. "high-scores" (2–42 chars, lowercase + hyphens)
gameIdYesUUID of the game to add the board to (from list_games)
sortDirNo"desc" for high-scores-win, "asc" for lowest-time-winsdesc
maxScoreNoOptional upper bound; scores above are rejected
minScoreNoOptional lower bound; scores below are rejected
scoreKindNoScore type: integer (default), duration_ms (time trials), or floatinteger
retentionNNoRequired when retentionPolicy="top_n": how many top scores to retain (1–1,000,000)
retentionPolicyNoHow long scores are kept: all (default), top_n (best N — set retentionN), or rolling_30d

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the board is added to an existing game and that the created board is returned with its id, but it omits auth requirements, error conditions, duplicate-slug behavior, and side effects.

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?

Four tightly written sentences, with the core action and scope front-loaded. Every sentence adds routing or usage value, and there is no redundant 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?

The schema fully documents parameters and the description states that the created board and its id are returned. For a creation tool with no annotations, it is nearly complete, but it stops short of describing permissions or failure modes.

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 description coverage is 100%, so all nine parameters are already documented in the schema. The description adds no parameter semantics beyond what the schema provides, including repeating the sortDir and gameId explanations.

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 and resource: add a leaderboard board to an existing game. It also distinguishes itself from the sibling bootstrap_leaderboard by explaining that this tool works only for already-existing games.

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?

Explicitly says to use this tool for existing games and names bootstrap_leaderboard as the alternative for brand-new games. It also tells the agent where to get gameId (list_games), leaving no ambiguity about when to invoke it.

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