Skip to main content
Glama

get_current_weather

Read-onlyIdempotent

Retrieve current weather for a coordinate to get temperature, apparent temperature, humidity, precipitation, wind, and a plain-language sky description.

Instructions

Current weather at a coordinate: temperature, apparent temperature, humidity, precipitation, wind, and a plain-language sky description.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_current_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety and idempotency are covered by structured data. The description adds the content of the response (which fields are reported), but nothing about units, latency, or failure modes for missing data. Useful but modest added value over the 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?

One compact sentence, front-loaded with the resource and coordinate scoping, then the payload fields. Every clause earns its place; no filler or repetition.

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?

With an output schema present, the description needn't explain return values, and annotations cover the safety profile, so the core is complete. The remaining gap is that units (metric vs imperial) and behavior for out-of-range or unavailable coordinates are left unstated, though the schema's range constraints partly mitigate this.

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% with both latitude and longitude fully documented including valid ranges, so the schema carries parameter meaning. The description only restates 'at a coordinate' without adding format or rounding guidance. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb+resource ('Current weather at a coordinate') and enumerates the returned measurements, so the agent knows exactly what it gets. The word 'Current' implicitly separates it from get_historical_weather and the forecast siblings, but no alternative is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the word 'Current' and the required coordinate inputs; an agent can infer this is the now-snapshot tool. However, there is no explicit when-to-use, when-not-to-use, or pointer to get_historical_weather / get_daily_forecast for other time ranges.

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