send-to-poke-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POKE_API_KEY | Yes | Your API key for Poke | |
| POKE_TIMEOUT | No | Timeout in milliseconds for requests | 30000 |
| POKE_BASE_URL | No | Base URL for Poke API | https://poke.com |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_to_pokeA | Send a message to Poke using the inbound webhook. |
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
Only one tool exists, so there is no possibility of confusion between tools. The purpose is singular: sending a message to Poke.
The single tool name follows a clear verb_noun pattern (send_to_poke), and with only one tool there are no inconsistencies to worry about.
The server has a single tool, which is minimal but appropriate for its extremely narrow scope of sending messages. It is slightly on the thin side but not unreasonable for a dedicated purpose.
For the stated purpose of sending messages via inbound webhook, the tool fully covers the operation. There are no obvious gaps in functionality.