Israel Hiking MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IHM_LOG_LEVEL | No | Set to DEBUG for verbose logging output. |
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 |
|---|---|
| pingA | Check that the server is alive and report its version and data attribution. This tool touches no upstream service. It is a placeholder used to verify transport and tool wiring, and will be removed once real tools exist. |
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 confusing it with other tools. The tool's purpose as a health check is clearly distinct.
The tool name 'ping' is a standard, recognizable term for a liveness check. While there is no pattern to compare against, the naming is unambiguous and follows common convention.
The server has only one placeholder tool, which is far too few for the domain implied by 'Israel Hiking MCP.' A single ping tool does not provide any substantive functionality.
The tool surface is severely incomplete. The server's purpose appears to be related to hiking, but no actual hiking tools exist; only a placeholder ping is provided, so there is no coverage of the domain.