Skip to main content
Glama
oaslananka

easyeda-mcp-pro

by oaslananka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List schematic nets

easyeda_schematic_nets
Read-onlyIdempotent

List nets from the current schematic context using focused scope; page/all_pages scopes are rejected on EasyEDA Pro 3.2.149.

Instructions

List nets from the current schematic context. Explicit focused scope is supported; page/all_pages scopes fail closed on EasyEDA Pro 3.2.149.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo
pageUuidNo
projectIdYesThe project/schematic ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
netsYes
errorNo
totalYes
error_codeNo
error_dataNo
project_idYes
read_scopeNo
not_availableNo
read_consistencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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"
    • addedInput schema / properties / pageUuid
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "enum": [
+    "focused",
+    "page",
+    "all_pages"
+  ],
+  "type": "string"
+}
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / error_code
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / error_data
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "focusedPageUuid": {
+      "type": "string"
+    },
+    "missingCapability": {
+      "type": "string"
+    },
+    "operation": {
+      "type": "string"
+    },
+    "pageUuid": {
+      "type": "string"
+    },
+    "requestedScope": {
+      "enum": [
+        "focused",
+        "page",
+        "all_pages"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / read_scope
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "focus_changed": {
+      "const": false,
+      "type": "boolean"
+    },
+    "focused_page_uuid": {
+      "type": "string"
+    },
+    "page_uuid": {
+      "type": "string"
+    },
+    "requested": {
+      "enum": [
+        "focused",
+        "page",
+        "all_pages"
+      ],
+      "type": "string"
+    },
+    "resolved": {
+      "enum": [
+        "focused",
+        "page",
+        "all_pages"
+      ],
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "requested",
+    "resolved",
+    "focus_changed",
+    "source"
+  ],
+  "type": "object"
+}
  2. Changed9 schema fields changedv0.19.1
    • addedInput schema / properties / projectId / description
      Added value: +"The project/schematic ID"
    • addedOutput schema / properties / error
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / nets / items / properties / canonical_net_name
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / nets / items / properties / imported_alias
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / nets / items / properties / net_kind
      Added value: +{
+  "enum": [
+    "signal",
+    "power",
+    "ground",
+    "power-flag",
+    "unnamed"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / nets / items / properties / normalization_rules
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / nets / items / properties / raw_net_name
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / nets / items / required
      Previous value: -[
-  "net_name",
-  "node_count",
-  "nodes"
-]New value: +[
+  "net_name",
+  "raw_net_name",
+  "canonical_net_name",
+  "net_kind",
+  "normalization_rules",
+  "imported_alias",
+  "node_count",
+  "nodes"
+]
    • addedOutput schema / properties / read_consistency
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "attempts": {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    "stable": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "stable",
+    "attempts"
+  ],
+  "type": "object"
+}
  3. First observedv0.19.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds beyond that by disclosing a version-specific behavioral constraint: page/all_pages scopes fail closed on EasyEDA Pro 3.2.149, warning the agent that those scopes will not return data.

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?

Two short, front-loaded sentences with zero filler. The core purpose comes first and the important scope caveat follows immediately.

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?

An output schema exists, so return values need not be explained. The description covers scope behavior and the version caveat, which are the main risks, but omits what focused scope means, how pageUuid interacts with scope, and the default when scope is omitted.

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 description coverage is only 33%, so the description must compensate. It adds meaningful semantics for the scope enum (focused works; page/all_pages fail closed) but leaves pageUuid and the default/omitted-scope behavior entirely undocumented in both schema and description.

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 (List) and resource (nets) with a clear context (current schematic). It implies a list-vs-detail distinction relative to the sibling easyeda_schematic_net_detail, but does not explicitly name or contrast with that sibling.

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 useful scope-selection guidance: focused scope is supported while page/all_pages fail closed on EasyEDA Pro 3.2.149. However, it never states when to use this tool versus alternatives like easyeda_schematic_net_detail, leaving tool selection to inference.

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