easyeda-mcp-pro

Health check

easyeda_health_check

Read-onlyIdempotent

Check server health status in one call, covering runtime version, bridge state, and EasyEDA version. Use after connecting the bridge extension for a single actionable status check.

Instructions

Return server health status in one call: runtime version, active profile, bridge state, EasyEDA version, keyless sourcing state, and starter catalog size. Intended as the single actionable status check after first connecting the bridge extension.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ups`	Yes
`status`	Yes
`profile`	Yes
`version`	Yes
`owner_pid`	No
`transport`	Yes
`owner_port`	No
`node_version`	Yes
`status_error`	No
`easyeda_version`	No
`bridge_connected`	Yes
`extension_version`	No
`registry_mismatch`	Yes
`catalog_device_count`	Yes
`keyless_sourcing_enabled`	Yes
`blocked_by_other_instance`	No
`extension_version_mismatch`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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 / owner_pid

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

addedOutput schema / properties / owner_port

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

addedOutput schema / properties / status_error
```
Added value: +{
+  "type": "string"
+}
```

Changed7 schema fields changedv0.19.1Jul 15, 2026

addedOutput schema / properties / catalog_device_count

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

addedOutput schema / properties / easyeda_version
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / extension_version
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / extension_version_mismatch
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / keyless_sourcing_enabled
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / registry_mismatch
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "status",
-  "version",
-  "node_version",
-  "profile",
-  "transport",
-  "bridge_connected",
-  "ups"
-]New value: +[
+  "status",
+  "version",
+  "node_version",
+  "profile",
+  "transport",
+  "bridge_connected",
+  "extension_version_mismatch",
+  "registry_mismatch",
+  "keyless_sourcing_enabled",
+  "catalog_device_count",
+  "ups"
+]

First observedv0.19.0Jul 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds the meaningful behavioral trait that this consolidates six signals 'in one call,' which is the reason to pick it over several narrower probes; it stops short of noting cost or refresh characteristics.

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 sentences, no filler. The payload list comes first and the usage cue second, so the agent gets the 'what' before the 'when' with nothing wasted.

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

Completeness5/5

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

Zero parameters, full annotation coverage, and an output schema that carries the return shape, so the description only needed to state the aggregate scope and the entry-point role — both are present. Nothing an agent needs to invoke it correctly is missing.

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 per the rubric this is the baseline 4. The description correctly implies a no-argument call ('in one call') and there is nothing further the schema leaves ambiguous.

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?

Names a specific verb and resource ('return server health status') and enumerates the exact payload (runtime version, profile, bridge state, EasyEDA version, keyless sourcing, catalog size), so it reads as an aggregate status roll-up. It does not explicitly differentiate itself from close siblings like easyeda_bridge_status or easyeda_get_server_config, so the agent must infer the boundary.

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?

Gives a clear situational trigger: 'the single actionable status check after first connecting the bridge extension.' That tells the agent when to reach for it rather than a narrower sibling, but it never names an alternative or states exclusions (e.g. after the bridge is already healthy, prefer bridge_status).

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

Deploy Server