Skip to main content
Glama
Spine Pipeline MCP

Spine Pipeline MCP

by RainLib

stage_asset_bundle

Creates an isolated JSON and referenced image bundle from a relative path without writing to source assets or including audio/sequences.

Instructions

Create an isolated JSON + referenced image bundle. No source writes. No audio/sequences.

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": {
      "relative_path": "<relative_path>"
    },
    "name": "stage_asset_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
relative_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

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 and destructiveHint=false, so the write-but-not-destructive profile is known. The description adds the meaningful claim that source files are never written, i.e. output is isolated. It does not say where the bundle is written, whether an existing bundle is overwritten, or what is returned.

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?

Three short front-loaded fragments with no filler; the resource is stated first and constraints follow. The telegraphic style is efficient but costs some precision.

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?

For a creation tool with one undocumented parameter and no output schema, the agent still lacks where artifacts land, the meaning of relative_path, and the failure/overwrite behavior. Annotations cover the safety profile, but the operational contract is incomplete.

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?

The single parameter relative_path has 0% schema description coverage, so the description carries the full burden and adds nothing: it never says what the path is relative to, whether it is a file or directory, or what constraints apply. This is the definition's largest gap.

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?

Specific verb 'Create' plus a concrete resource: an isolated JSON bundle plus referenced images. The scope limits ('No audio/sequences') narrow it against siblings such as stage_json_copy, though it never names an alternative explicitly.

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?

The exclusions ('No source writes', 'No audio/sequences') imply when this tool is inappropriate, which is useful negative guidance. But there is no positive statement of when to pick this over stage_json_copy or animation_copy, so selection is still partly inferential.

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