Skip to main content
Glama
oaslananka

easyeda-mcp-pro

by oaslananka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get feature flags

easyeda_get_feature_flags
Read-onlyIdempotent

Retrieve current feature flag values to identify enabled profile-gated tools in EasyEDA Pro.

Instructions

Return current feature flag values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
flagsYes
maturityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • addedOutput schema / properties / 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: -[
-  "flags"
-]New value: +[
+  "flags",
+  "maturity"
+]
  2. First observedv0.19.0

TDQS

B3.1/5.0
Behavior2/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 nothing beyond that — no note on whether flags are per-project, cached, or mutable server-side state, which is the kind of context that would justify a higher score.

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?

One short sentence with no filler, and the resource is front-loaded. It is efficient, though it is arguably under-specified rather than deliberately tight.

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

Completeness3/5

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

With no parameters and an output schema present, return-value explanation is unnecessary, so the description is close to sufficient. The remaining gap is routing: nothing tells the agent how this differs from the other easyeda_get_* introspection 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 and resource ('Return ... feature flag values'), so an agent knows it reads runtime feature-flag state rather than design data. However, it offers no differentiation from nearby read-only siblings such as easyeda_get_capabilities, easyeda_get_server_config, or easyeda_get_tool_profiles.

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?

There is no statement of when to call this versus the other introspection tools, nor any prerequisite or exclusion. The agent must infer usage purely from the name.

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