MCP Basic Create Tool
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherB | Gets the weather for a given location. |
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 agent will always select 'get_weather' for weather queries.
With only one tool, no naming inconsistencies exist. The name 'get_weather' follows a clear verb_noun pattern.
A single tool is extremely limited for a server named 'MCP Basic Create Tool', which suggests a broader scope. Additionally, the only tool is a weather lookup, not a creation tool, making the count inappropriate.
The server provides only a basic weather retrieval tool. For a weather domain, one would expect additional operations like forecast, historical data, or location search, but none are present.