Skip to main content
Glama

Open Archives

by io.github.coret

Historical Weather

get_historical_weather
Read-only

Historical weather measurements for a date and location

Returns historical weather measurements from the nearest Dutch weather station for the specified date and coordinates. Data sources are the Royal Netherlands Meteorological Institute (KNMI): measurements 1701–1905 and 1901–2014. Note: this endpoint exposes several types of historical datasets, so measurement types and units can vary between records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
langNo
latitudeYes
longitudeYes

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint/openWorldHint. The description adds context about KNMI data sources, two time ranges, and warns that measurement types/units vary, which is useful beyond annotations.

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?

Two sentences, no filler, mentions key caveat about data variability. Could be slightly tighter but overall well-structured.

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

Completeness3/5

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

The tool has 4 params, no output schema, and the description covers Dutch scope, source, and variability but leaves response shape and units unspecified. Given openWorldHint, it's adequate but not complete.

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 coverage is 0%; the description references date and coordinates but doesn't define date format, coordinate system, or the lang parameter. It adds minimal semantic value beyond property names.

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?

The description explicitly states it 'Returns historical weather measurements from the nearest Dutch weather station for the specified date and coordinates' — a specific verb+resource+scope that clearly distinguishes it from the sibling genealogy/transcription tools.

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?

The description makes the use case clear: nearest Dutch station, historical dates, but no explicit comparison to alternatives or exclusions. Since siblings are obviously unrelated, a 4 is appropriate.

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

All Open Archives toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, e.g., browse/search/show/view transcriptions are well differentiated. The stats tools (get_event_type_stats vs get_source_type_stats vs get_record_stats) are similar in structure but each targets a unique dimension, and names make the distinction clear.

Naming Consistency3/5

All tools use snake_case and are descriptive, but they mix verb prefixes: browse, get, match, search, show, view. This is not fully consistent, though each verb aligns with the action. Some names like get_births_years_ago are less patterned than others.

Tool Count3/5

With 22 tools, the set is on the heavier side but justifiably covers diverse features: genealogical records, transcriptions, statistics, weather, census, and archives. It borders on too many, but the scope is broad enough to support them.

Completeness4/5

The domain of genealogical archives is well covered with search, show, browse, stats, and matching tools. Minor gaps exist (e.g., no explicit user comment tools beyond stats, no direct archive detail endpoint separate from list), but core workflows are supported.

Resources