Skip to main content
Glama
Sign In
@splice-cad/mcp

@splice-cad/mcp

Official
by splice-cad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

save_plan

Save the complete PlanData JSON to a project, overwriting its existing plan data. Use get_plan to fetch the current state before applying changes.

Instructions

Save (overwrite) the PlanData JSON for a project. The plan_data must be a complete, valid PlanData object. Read the plan_schema resource first to understand the structure. Use get_plan to fetch the current state before modifying.

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": {
      "project_id": "<project_id>",
      "plan_data": "<plan_data>"
    },
    "name": "save_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_dataYesComplete PlanData JSON object
project_idYesProject UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and clearly discloses the destructive overwrite behavior, the requirement for a complete and valid object, and the need to fetch current state to avoid data loss. It does not cover auth or error behavior, but the key behavioral traits are transparent.

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?

Three focused sentences, front-loaded with the purpose, then concise usage guidance. No wasted words or redundant content.

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?

For a save/overwrite tool with a nested object, the description gives the essential workflow (read schema, fetch current state) and the completeness requirement. It omits return value or failure behavior, but for a write operation the context is largely sufficient.

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 descriptions already explain both parameters (project_id as UUID, plan_data as Complete PlanData JSON object). The description adds 'valid' and 'overwrite' semantics, but this is marginal; it does not meaningfully go beyond the schema.

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?

The description clearly states 'Save (overwrite) the PlanData JSON for a project', using a specific verb and resource, and the overwrite qualifier distinguishes it from read-only siblings like get_plan and validate_plan.

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

Usage Guidelines4/5

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

It provides explicit context: read plan_schema first, fetch current state with get_plan before modifying. This gives clear prerequisites and sequencing, though it does not enumerate when not to use it (e.g., for validation).

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

Deploy Server

Other Tools