Skip to main content
Glama
oaslananka

easyeda-mcp-pro

by oaslananka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Modify schematic primitive

easyeda_schematic_modify_primitive

Safely modify schematic primitives while preserving omitted fields. Automatically snapshots changes and restores prior state if write fails, keeping wires attached.

Instructions

Safely modify a schematic primitive while preserving omitted fields. With transactionId and projectId, capture before/after snapshots and automatically restore the prior state if the write or post-write read fails. Component moves keep connected wires attached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyYes
projectIdNoRequired when transactionId is supplied; must match the transaction document.
primitiveIdYes
confirmWriteYesMust be the literal boolean true (not the string "true") to allow this write.
transactionIdNoOptional snapshot-backed project transaction ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.19.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv0.19.1
    • addedInput schema / properties / confirmWrite / description
      Added value: +"Must be the literal boolean true (not the string \"true\") to allow this write."
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Required when transactionId is supplied; must match the transaction document.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / transactionId
      Added value: +{
+  "description": "Optional snapshot-backed project transaction ID.",
+  "minLength": 1,
+  "type": "string"
+}
  3. First observedv0.19.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing merge semantics (omitted fields preserved), automatic before/after snapshots with rollback if the write or post-write read fails, and that component moves keep connected wires attached. These are exactly the behavioral traits an agent needs for a mutation tool.

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 tightly packed sentences, each earning its place: safety/merge behavior first, transactional rollback second, wire-preservation third. No filler or repetition.

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 5-parameter mutation tool with an output schema and only partial schema coverage, the description covers the critical rollback, merge, and connectivity semantics. It omits primitiveId semantics and any note about what property keys are valid, so it's strong but not fully complete.

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

Parameters4/5

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

Schema coverage is 60%; the description compensates by explaining that property is a partial update that preserves omitted fields, and by clarifying the transactionId/projectId snapshot pairing. primitiveId remains undocumented, keeping it from a 5.

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 (modify) and resource (schematic primitive), and adds the key constraint that omitted fields are preserved, which distinguishes it from add/delete siblings. It does not explicitly name alternatives like batch_write, so it lacks full sibling differentiation.

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?

Usage is implied: single-primitive partial modification, optionally wrapped in a snapshot-backed transaction. The description explains the transactional mode but gives no explicit when-to-use/when-not guidance or named alternatives (e.g., batch_write for multiple primitives).

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