MCP Evolution API
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVOLUTION_API_KEY | Yes | Your Evolution API key for authentication | |
| EVOLUTION_API_URL | Yes | The URL of your Evolution API server |
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 |
|---|---|
| hello_toolD | Hello tool |
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 compare it against. The single tool's purpose is inherently distinct by default.
A single tool cannot demonstrate inconsistency, as there are no other tool names to compare it to. The naming pattern for 'hello_tool' (snake_case) is consistent within the set, albeit trivially so.
A single tool is generally too few for most server purposes, as it limits functionality and suggests an incomplete or trivial implementation. While it might be appropriate for a minimal 'hello world' server, it is inadequate for any substantive domain coverage.
With only one tool named 'hello_tool', it is impossible to infer a meaningful domain or assess coverage. There are obvious gaps, as no CRUD operations, lifecycle management, or typical API interactions are present, making the surface severely incomplete for any practical purpose.