MCP Playground
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILTRAP_API_TOKEN | No | Your Mailtrap API key for sending emails |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_usersD | – |
| get_all_employee_profilesD | – |
| send_emailD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| compose_team_for_project |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| db_schema |
TDQS
Scored across 3 tools
get_users and get_all_employee_profiles likely serve similar purposes, potentially causing confusion. Without descriptions, an agent may select the wrong tool.
All tools follow a verb_noun pattern (get_, send_), but the noun forms are inconsistent: 'users' versus 'all_employee_profiles' and 'email'.
With only 3 tools, the set is small but might be adequate for a simple playground. The count is borderline but not extreme.
Missing basic CRUD operations for users/employees (create, update, delete) and limited email functionality (only send). Significant gaps for a typical management domain.