DatoQA

get_weather

Read-onlyIdempotent

Official NWS forecast for one supported US city grid point; use list_weather_locations for city ids. Celsius day/night forecast highs/lows, not current observed weather or alerts. English source text, explicit periods and source update time. Hourly retrieval, expires within two hours. Not independently verified.

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_weather"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	Supported US grid-point identifier from list_weather_locations; not a free-text city name or worldwide location.

Output Schema

Name	Required	Description
`items`	Yes
`notice`	No
`status`	Yes	Read this before using values; a successful transport does not establish data availability.
`returned`	Yes	Domain-specific result count, not necessarily the number of stored records in items.
`directory`	No
`independently_verified`	No	Official-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedSep 27, 2026

changedOutput schema / properties / items / items / properties / provenance / properties / verification_level / enum

Previous value: -[
-  "official_source_and_schema_checked",
-  "method_specific"
-]New value: +[
+  "official_source_and_schema_checked",
+  "public_aggregator_and_schema_checked",
+  "method_specific"
+]

First observedSep 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: forecast freshness ('expires within two hours'), hourly retrieval cadence, the source's own update time, English source text, and an explicit provenance caveat ('Not independently verified'). This is well beyond what the structured fields convey.

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?

Dense but front-loaded: purpose first, then routing, then exclusions, then output/caveat details. Every clause carries non-redundant information and nothing is padding, even though the phrasing is telegraphic.

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

Completeness5/5

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

An output schema exists, so return-value explanation is unnecessary; the description still supplies the units (Celsius), period structure (day/night highs/lows), and source language. Combined with 100% schema coverage and full annotations, an agent has everything needed to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the single 'city' parameter is already documented in the schema as a grid-point id, not a free-text name. The description reinforces this ('one supported US city grid point') but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

Names a specific verb+resource ('Official NWS forecast') and pins scope precisely ('one supported US city grid point'). It also draws a clear boundary against what it is not ('current observed weather or alerts'), which lets an agent separate it from the other get_* siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent to list_weather_locations to obtain city ids, and states the exclusions (not current observed weather, not alerts). Both the when-to-use and when-not-to-use conditions are stated directly.

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

All DatoQA tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?