Plugin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TUNNEL_ID | Yes | The Tunnel ID used to configure the local connection with the setup wizard. | |
| ORGANIZATION_ID | Yes | The Organization ID used to configure the local connection with the setup wizard. | |
| RUNTIME_API_KEY | Yes | The Runtime API key, entered using hidden input and stored locally with Windows DPAPI. | |
| LOCAL_HEALTH_PORT | Yes | The local health port. It is validated before it is saved. |
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 |
|---|---|
| plugin_statusB | Return basic runtime identity. Supports SHA-256 conditional reads so unchanged payloads can be suppressed, and optional short TTL reuse can skip safe read execution. |
| plugin_echoD | Minimal example tool. Replace or remove this when implementing the real plugin. |
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 2 tools
plugin_status and plugin_echo have distinct roles—one returns runtime identity, the other is an example echo—so they are not easily confused. However, plugin_echo's purpose is intentionally under-specified as a placeholder, leaving slight ambiguity about its intended use.
Both tools follow the same plugin_ prefix with snake_case noun suffixes (status, echo), giving a fully predictable naming pattern. There is no mixing of conventions or verb styles.
Two tools is thin for any server, and one is explicitly a placeholder to be replaced, so the set feels under-scoped. This is borderline rather than extreme, since a plugin scaffold might legitimately start small.
The surface has no real domain operations—just runtime identity and a placeholder echo—so it cannot support actual plugin workflows. Significant gaps remain before this could serve as a functional MCP server.