Skip to main content
Glama

Remix a public board

remix_board
Idempotent

Make the user's own public remix of a public board, after get_board_remix_preview, only when the user asked to remix, fork or copy it to change it. Copies every published version up to the previewed one into a new public board in their account that credits the original author; it never changes the original. Pass the preview's previewToken and visibility "public". Refused when the user already has a remix of the board unless again is true, when the board is itself a remix still copying its files, past 10 remixes a day, or when it does not fit. Returns the remix ready to read and change, with no waiting; its files finish copying into the user's storage in the background (filesCopying), which blocks nothing. Retrying with the same previewToken returns the same remix, even after the preview expires.

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": {
      "board": "<board>",
      "previewToken": "<previewToken>",
      "visibility": "<visibility>"
    },
    "name": "remix_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
againNotrue to make another copy when the user already has a remix of this board.
boardYesThe public board to remix: handle/slug or a boardrepo.com URL.
versionNoA published version number to remix up to; omit for the latest.
visibilityYesA remix is always public and credits the original's author; pass "public" to acknowledge it.
previewTokenYespreviewToken from get_board_remix_preview for this same board and version.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true; the description adds substantial context beyond that. It discloses scope (copies every published version up to the previewed one), that the original is never modified, a daily limit of 10 remixes, the existing-remix conflict and the 'again' escape hatch, deferred background file copying via filesCopying, and that retries with the same previewToken are safe even after preview expiry — consistent with idempotentHint.

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 prerequisite and the trigger condition are front-loaded, and every sentence carries operational information — refusals, background copying, retry identity. The middle sentences are densely packed with clauses ('Refused when... unless... when... or when...'), which costs some readability but not enough to justify trimming.

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 mutating, rate-limited, otherwise-world tool with a prerequisite sibling, the description covers the trigger, the ordering, all refusal paths, side effects on both the new and original board, and eventual-consistency of file copying. An output schema exists, so not restating the return shape is appropriate, and the one return detail given (filesCopying) is the non-obvious asynchronous part.

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 the baseline is 3, but the description adds real meaning: previewToken must be tied to the same board and version previewed, and reuse of it returns the same remix rather than a duplicate. Visibility is framed as an acknowledgement the agent must pass as 'public', which clarifies intent rather than restating the const.

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: makes the user's own public remix of a public board, copying published versions into a new board that credits the original author. It also explicitly separates itself from its prerequisite, get_board_remix_preview, so an agent can tell which call creates the remix versus which one previews it.

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 an explicit trigger ('only when the user asked to remix, fork or copy it to change it') and an explicit ordering constraint ('after get_board_remix_preview'), naming the sibling that must run first. It also enumerates the conditions under which the call is refused, which is the when-not guidance most tools omit.

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