Skip to main content
Glama
kukapay

eips-mcp

by kukapay
OverviewSchemaRelated ServersScoreDiscussions
Python

search

Find Ethereum Improvement Proposals (EIPs) by entering search terms to locate relevant protocol specifications and standards.

Instructions

Search Ethereum EIPs by query string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:25-34 (handler)
    The handler function for the MCP 'search' tool, registered via @mcp.tool(). It searches the EIP knowledge base for the given query, retrieves the top 5 matching document chunks, and returns a formatted string with separators and content.
    @mcp.tool()
def search(query: str) -> str:
    """Search Ethereum EIPs by query string"""
    # Implementation to be added
    chunks = knowledge_base.search(query=query, num_documents=5)
    parts = []
    for chunk in chunks:
        parts.append("-" * 20 + chunk.name + "-" * 20)
        parts.append(chunk.content)
    return "\n".join(parts)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It lacks details on rate limits, authentication needs, response format (though output schema exists), pagination, or error handling, which are critical for a search operation.

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?

The description is extremely concise and front-loaded, consisting of a single, direct sentence that states the tool's purpose without any unnecessary words. Every part of the sentence earns its place by conveying essential information efficiently.

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?

Given the tool's low complexity (one parameter) and the presence of an output schema, the description is minimally adequate. However, it lacks details on behavioral aspects like search scope or limitations, making it incomplete for fully informed use despite the output schema covering return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not compensate by explaining the 'query' parameter's semantics, such as expected format, examples, or search behavior. It merely mentions 'by query string' without adding meaningful context beyond the schema's structure.

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?

The description clearly states the tool's purpose with a specific verb ('Search') and resource ('Ethereum EIPs'), making it immediately understandable. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It merely states what the tool does without indicating appropriate scenarios or limitations, leaving usage entirely implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kukapay/eips-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server