eips-mcp
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Search Ethereum EIPs by query string |
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 possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The single tool's purpose is clearly defined and distinct by default.
Since there is only one tool, it inherently maintains perfect consistency with itself. The naming follows a simple, clear verb pattern ('search') that aligns with its function.
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or minimalistic implementation. For a domain like Ethereum EIPs, more operations (e.g., get details, list categories, filter by status) would be expected to provide comprehensive coverage.
The tool surface is severely incomplete for searching Ethereum EIPs; it only offers a basic search function without supporting operations like retrieving specific EIP details, browsing by number or status, or accessing related metadata. This will likely cause agent failures when more nuanced interactions are needed.