Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_forecast

Retrieve a 7-day weather forecast for any city. Includes daily high/low temperatures, precipitation, and weather condition codes.

Instructions

Get a 7-day weather forecast for any city.

Uses Open-Meteo (free, no key) after geocoding the city via Nominatim.
Returns daily high/low temps, precipitation, and weather codes.

Parameters:
    city — City name to get forecast for (required), e.g. "London".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "get_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses external API dependencies and response elements (temps, precipitation, weather codes), but lacks details on error handling (e.g., unrecognized city) or rate limits. No annotations present, so description carries burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise paragraphs, front-loaded with main purpose, no redundant sentences. Efficiently structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, parameter details, and dependencies. Output schema likely provides return format details, so missing response structure is acceptable. Minor omission: no mention of error cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning to the single parameter 'city' with a description and example ('e.g., 'London''), compensating for 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'Get', specific resource '7-day weather forecast', and scope 'any city'. Distinguishes from sibling 'get_weather' by specifying duration and free API source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States when to use (free, no API key) and explains geocoding dependency, but does not explicitly list when not to use or compare with alternatives like 'get_weather'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools