Skip to main content
Glama

get_historical_weather

Read-only

Historical weather observations between ISO dates.

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": {
      "location": "<location>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_historical_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
locationYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds only the historical scope and ISO date constraint, omitting data sources, timezone handling, availability limits, auth, and rate limits. With annotations covering the safety profile, this is adequate but thin.

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

Conciseness4/5

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

A single compact phrase with no wasted wording, and the historical scope is front-loaded. It is under-specified rather than verbose, so conciseness is strong but does not compensate for missing detail.

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

Completeness2/5

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

The presence of an output schema means return values need not be described, but the input side is incomplete for a tool requiring a nested location object at 0% schema coverage. Critical invocation details such as location shape and date-range expectations are left undocumented.

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

Parameters2/5

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

Schema description coverage is 0% and there are three required parameters, including a nested location object. The description only hints that dates are ISO-formatted; it does not explain location structure, accepted date ranges, timezone semantics, or whether end_date is inclusive.

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

Purpose4/5

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

The description states a specific resource (historical weather observations) and a temporal constraint (between ISO dates). It implicitly distinguishes itself from current/forecast siblings through "historical," but does not explicitly name or contrast them.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. An agent must infer from the word "historical" that this is for past observations rather than forecasts or current conditions, with no explicit alternatives or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.