easyeda-mcp-pro

Get capabilities

easyeda_get_capabilities

Read-onlyIdempotent

Retrieve the EasyEDA Pro MCP server's available profiles, enabled feature flags, and supported operations to determine which design review and export tools are active.

Instructions

Return server capabilities, including available profiles, enabled feature flags, and supported operations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`profiles`	Yes
`transports`	Yes
`server_name`	Yes
`feature_flags`	Yes
`server_version`	Yes
`current_profile`	Yes
`feature_maturity`	Yes
`protocol_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 / feature_maturity

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "configured": {
+        "type": "boolean"
+      },
+      "effective": {
+        "type": "boolean"
+      },
+      "maturity": {
+        "enum": [
+          "implemented",
+          "experimental",
+          "reserved"
+        ],
+        "type": "string"
+      },
+      "note": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "maturity",
+      "configured",
+      "effective",
+      "note"
+    ],
+    "type": "object"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "server_name",
-  "server_version",
-  "protocol_version",
-  "profiles",
-  "current_profile",
-  "feature_flags",
-  "transports"
-]New value: +[
+  "server_name",
+  "server_version",
+  "protocol_version",
+  "profiles",
+  "current_profile",
+  "feature_flags",
+  "feature_maturity",
+  "transports"
+]

First observedv0.19.0Jul 4, 2026

TDQS

B3.4/5.0

Behavior3/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 what is returned (profiles, flags, operations), but since an output schema exists, that content is largely redundant rather than additive behavioral context.

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?

A single front-loaded sentence with no filler. Slightly padded by listing return contents that the output schema already documents, but nothing is wasted.

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?

With an output schema present, no-arg invocation, and annotations covering safety, the description supplies enough for an agent to call it correctly. The only real omission is how it relates to the narrower sibling tools.

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?

Zero parameters, so there is nothing to disambiguate; the baseline for a no-param tool is 4. The description correctly implies no input is needed.

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 (Return) and resource (server capabilities) and enumerates the contents: profiles, feature flags, supported operations. However, it does not differentiate itself from close siblings like easyeda_get_feature_flags, easyeda_get_tool_profiles, and easyeda_get_server_config, 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 to call this versus the more targeted siblings (get_feature_flags, get_tool_profiles, get_server_config). An agent must infer that this is the broad aggregate call rather than the narrow one.

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

Deploy Server