Erick Wendel Contributions 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 |
|---|---|
| get_talksC | Get a list of talks with optional filtering and pagination. |
| get_postsB | Get a list of posts with optional filtering and pagination. |
| get_videosC | Get a list of videos with optional filtering and pagination. |
| check_statusA | Check if the API is alive and responding. |
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 4 tools
Each tool has a clearly distinct purpose targeting different resource types: API status, posts, talks, and videos. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (check_status, get_posts, get_talks, get_videos), using snake_case throughout. This predictability enhances readability and usability for agents.
With 4 tools, the count is reasonable for a contributions-focused server, covering status and three content types. It feels slightly thin but well-scoped, as each tool serves a distinct purpose without unnecessary bloat.
The toolset provides read-only access to posts, talks, and videos with filtering and pagination, which is adequate for retrieval. However, there are notable gaps: no create, update, or delete operations, limiting full lifecycle management of contributions in the domain.