Weather By Api Ninjas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for Weather By Api Ninjas API |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1weatherD | API Ninjas Weather API endpoint. |
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 one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as accessing a weather API endpoint, making it unambiguous in isolation.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'v1weather' follows a clear pattern (version prefix + descriptive term), though this cannot be evaluated for consistency across multiple tools.
A single tool is generally too few for a weather API server, as it limits functionality to a basic endpoint without supporting related operations like forecasts, historical data, or location searches. This feels thin and under-scoped for the domain.
The tool surface is severely incomplete for a weather domain, covering only a basic endpoint. Missing are common operations such as multi-day forecasts, severe weather alerts, or location-based queries, which will likely cause agent failures when more comprehensive weather data is needed.