Skip to main content
Glama

Get current conditions

get_current_conditions
Read-only

Retrieve current National Weather Service station observations nearest a US place or coordinates, including temperature, wind, humidity, pressure, visibility, and reading age.

Instructions

Latest observation from the National Weather Service station nearest a US location: temperature, wind, humidity, pressure, visibility, and how old the reading is.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_current_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoUS place name to look up, as "City, ST" (e.g. "Tucson, AZ") or a full street address. Provide either this or latitude+longitude, not both.
latitudeNoLatitude in decimal degrees. Must be paired with longitude.
longitudeNoLongitude in decimal degrees. Must be paired with latitude.
response_formatNomarkdown for a compact human/LLM-readable summary, json for the structured object.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: the data source is NWS, the reading comes from the nearest station (so it is spatially approximate), it is US-only, and it reports data staleness ('how old the reading is'). It stops short of noting units or behavior when no station is found.

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?

A single front-loaded sentence that names the source, the resource, the resolution strategy, and the fields returned. No filler or redundant restatement of the title.

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 no output schema, listing the returned fields and the staleness indicator is exactly what an agent needs. The main remaining gap is units and the no-station-nearby case, but overall it is sufficient to call the tool correctly.

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?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by stating the tool is limited to US locations, a constraint the place/latitude/longitude schema does not mention. It still says nothing about how 'place' resolves to a station versus explicit coordinates.

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 and resource: 'Latest observation from the National Weather Service station nearest a US location,' plus the exact quantities returned. The word 'observation' implicitly separates it from the sibling forecast tools, though no sibling 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 only implied by the phrase 'latest observation' versus the forecast siblings. There is no explicit statement of when to prefer this over get_forecast or get_hourly_forecast, and no note about failure when no station is nearby.

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