mcp-pin
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weatherC | Get the current weather for a city. |
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 overlap or confusion; the tool has one clear purpose. An agent cannot misselect because there is nothing else to select.
The lone tool uses a plain noun ('weather') rather than a verb_noun pattern, but with only one tool there is no internal inconsistency to penalize. It is readable and predictable enough.
A single trivial tool is far too thin for a standalone server, and the server name 'mcp-pin' gives no indication of weather functionality. One tool provides almost no surface for an agent to work with.
The weather domain is barely covered: only current conditions for a city, with no forecast, hourly/daily breakdown, historical data, or location lookup. This creates dead ends for most realistic weather queries.