easyeda-mcp-pro

Bridge status

easyeda_bridge_status

Read-onlyIdempotent

Verify EasyEDA Pro bridge connectivity, version, and capabilities to confirm proper setup for AI-assisted hardware design.

Instructions

Check EasyEDA Pro bridge connection status, version, and capabilities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`dev_mode`	No
`connected`	Yes
`owner_pid`	No
`uptime_ms`	No
`owner_port`	No
`diagnostics`	No
`capabilities`	No
`status_error`	No
`bridge_version`	No
`easyeda_version`	No
`last_heartbeat_ms`	No
`blocked_by_other_instance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.19.2Oct 2, 2026

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"

addedOutput schema / properties / blocked_by_other_instance
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / diagnostics / properties / blocked_by_other_instance
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / diagnostics / properties / owner_pid

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / diagnostics / properties / owner_port

Added value: +{
+  "maximum": 65535,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / owner_pid

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / owner_port

Added value: +{
+  "maximum": 65535,
+  "minimum": 1,
+  "type": "integer"
+}

First observedv0.19.0Jul 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that version and capabilities are included in the response, a small amount of context beyond the structured fields, but no detail on what 'capabilities' means or connection failure behavior.

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?

A single efficient sentence that front-loads the primary purpose and appends the secondary returns. No filler.

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 detailed in prose, and a zero-parameter read-only status tool is inherently simple. Slight gap: no hint about what the bridge status values mean or how to react to a disconnected state.

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?

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. Nothing in the description is required to explain inputs.

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 ('Check') and resource ('EasyEDA Pro bridge connection status') plus the fields returned (version, capabilities). However, it does not distinguish itself from adjacent siblings like easyeda_health_check or easyeda_get_capabilities, which cover overlapping ground.

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

Usage Guidelines2/5

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

No guidance on when this should be used versus easyeda_health_check, easyeda_get_feature_flags, or easyeda_get_capabilities, all of which appear to query related state. The agent must infer the distinction from names alone.

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

Deploy Server