Skip to main content
Glama

Save to a board

save_to_board
Destructive

Save published scenes to a private account board shared with the Launchscene website. Requires an account and write scope.

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": {
      "scene_ids": "<scene_ids>"
    },
    "name": "save_to_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
board_idNo
scene_idsYes
board_nameNo

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=false, so the description is not the sole carrier of the safety profile. It does add value the annotations cannot: the destination is a private board that is shared out to the Launchscene website, plus the auth/scope requirement. What it fails to disclose is the consequence implied by destructiveHint — whether saving into an existing board replaces or appends to its contents, and whether board creation is a side effect.

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?

Two compact sentences with the operation stated first and the account/scope constraint second; nothing is padded or repeated from the title. It is efficient but under-built for the parameter ambiguity it leaves behind.

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

Completeness2/5

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

An output schema exists, so return values need no explanation, but this is a destructive four-parameter mutation with zero schema descriptions and the description does not close that gap. The board targeting/creation semantics and the overwrite behavior flagged by destructiveHint=true are exactly what an agent needs before calling it, and both are missing.

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

Parameters2/5

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

Schema description coverage is 0% for four parameters, so the description must compensate and it does not. It never explains the relationship between board_id and board_name (mutually exclusive? one creates, one targets?), nor what note attaches to, nor that scene_ids is capped at 20 items — an agent must guess whether supplying both board fields is an error.

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 verb and resource: save published scenes onto a private account board. The scope qualifier 'published scenes' and 'private account board' meaningfully narrows what the tool does, and the direction of the operation (writing into a board, not reading from it) is unambiguous. It does not explicitly differentiate itself from the board-oriented sibling list_boards, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives prerequisites (requires an account and write scope) and a precondition that only published scenes qualify, which is real usage context. However, it never names an alternative or an exclusion case — an agent cannot tell from this whether list_boards is the read counterpart, or when to create a board versus reuse one.

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