@splice-cad/mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_live_state

Retrieves live frontend state for a given namespace, including unsaved plan and assembly data. Use specific queries to get component state, summary data, or mutation status for the active tab.

Instructions

Get or set live frontend state. Reflects all unsaved changes, including for assemblies (harness:* namespace). Use setComponentState to update the Component Creator form fields.

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": {
      "query": "<query>"
    },
    "name": "get_live_state"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Plan (project:): getData (PlanData), getSummary (counts). Assembly (harness:): getData (BOM + connections + positions), getSummary (part/connection counts). Both: canUndo, canRedo. Component creator: getComponentState, getSvgElements, setComponentState.
`params`	No	Parameters for mutations like setComponentState. Keys: form (mpn, manufacturer, description, img_url, datasheet_url), spec (gender, shape, category, positions, rows, series, pitch_mm, wire_awg_min, wire_awg_max), svg (clear, elements, pins), action ("save" to save component, "createNew" to reset)
`namespace`	No	Target tab namespace

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal that the tool reflects unsaved changes and that setComponentState updates form fields, but it does not mention potential persistence side effects of the 'save' action found in the schema, nor other mutation risks beyond the term 'set'.

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 description is brief, two sentences, with key information front-loaded. It wastes no words and quickly conveys the dual get/set nature and the specific setter use case.

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

Completeness3/5

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

Given the three parameters, nested object, and absence of output schema, the description is somewhat minimal. It explains the high-level purpose and one use case, but it does not describe return value shapes or the full scope of queries, leaving the schema to fill in gaps. This is sufficient but not exhaustive.

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?

The schema provides 100% parameter description coverage, including detailed meanings for each query value and params structure. The description adds little beyond what the schema already states, like the namespace reference, but it does reinforce the setComponentState usage.

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?

The description clearly states the tool gets or sets live frontend state and explicitly mentions that it reflects unsaved changes, including assemblies. It distinguishes the tool by highlighting the harness:* namespace and component creator setter functionality, though it does not name sibling tools for direct comparison.

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 description gives one explicit usage instruction: 'Use setComponentState to update the Component Creator form fields.' It also implies the tool is appropriate when unsaved state matters, but it does not provide exclusions or contrast with alternative tools like get_plan_summary or get_harness_summary.

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