Skip to main content
Glama

Preview a remix of a public board

get_board_remix_preview
Read-onlyIdempotent

Before remix_board: say what remixing a public board into the user's account would make. A remix is the user's own public copy of the whole history up to a version, crediting the author, that they can then change and save versions of. Returns the name (a remix keeps the original's; the user can choose another with Remix on the web page), version, licence note, size against free space, any existing remix, whether the board is itself a remix still copying its files (then it cannot be remixed yet), and a previewToken plus operationId for remix_board, valid 15 minutes. Tell the user the remix is public, its licence and its size; if they already asked to remix, no further confirmation is needed. Reads only.

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>"
    },
    "name": "get_board_remix_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesThe public board to remix: handle/slug or a boardrepo.com URL.
versionNoA published version number to remix up to; omit for the latest.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds material behavior beyond them: the previewToken/operationId pair handed to remix_board with a 15-minute expiry, the fact the remix is a public copy crediting the author, name inheritance, and the copy-in-progress blocker. It also states the disclosure duty (tell the user it is public, its licence and size).

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-loaded with the trigger condition and the definition of a remix before the field inventory. The enumeration of returned values is somewhat long given an output schema exists, but each item carries actionable instruction (report licence and size, stop on a copy-in-progress board) rather than filler.

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?

Covers the full workflow: when to call it, what it returns, what the token is for and how long it lasts, what to tell the user, and when confirmation can be skipped. Despite the output schema existing, the extra behavioral detail is enough for an agent to call it and act on the result correctly.

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 both parameters are already documented, and the description mostly restates them. It adds only light semantics, clarifying that a remix copies the whole history up to the chosen version and that the name is inherited unless changed on the web page. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Opens with a specific verb and resource tied to the sibling it precedes ('Before remix_board: say what remixing a public board into the user's account would make'), then defines what a remix is. An agent can distinguish this dry-run preview from the actual remix_board mutation without opening either schema.

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 names the sequencing ('Before remix_board') and gives the alternative path: if the user already asked to remix, no further confirmation is needed. It also states a blocking condition (a board that is itself a remix still copying files cannot be remixed yet), which is exactly the when-not guidance an agent needs.

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