JungleBridge 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_connection_statusA | Return scaffold status only; does not verify or contact the WTTJ API. |
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 a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly stated, albeit limited.
The single tool follows the snake_case verb_noun pattern (get_connection_status), which is consistent and predictable.
A server with only one trivial tool that merely returns a scaffold status without any real API interaction is an extreme mismatch for the apparent purpose of a JungleBridge MCP. It feels like a placeholder rather than a functional server.
The tool does not actually verify or contact the WTTJ API, and there are no other tools to cover any meaningful operations. The surface is severely incomplete and would cause agent failures.