EDS Block Analyser MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eds_block_analyserB | Get a UI architect prompt for analyzing and estimating UI block conversion from Figma designs or web pages |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity or overlap. The tool's purpose is clearly defined and distinct from any potential alternatives.
The single tool name follows a descriptive pattern and has no conflicting conventions. Consistency is trivially maintained with one tool.
The server has only one tool, which feels thin for a typical MCP server. While the tool is non-trivial and serves a specific purpose, the limited scope makes the count borderline.
The tool fully addresses its stated purpose of generating a UI architect prompt for UI block analysis and estimation. There are no obvious gaps or missing operations for this narrow domain.