Skip to main content
Glama

get-weather

Fetch current weather conditions by city name or latitude and longitude coordinates for location-based weather lookups.

Instructions

Get current weather conditions for a location. Provide either a city name OR latitude+longitude coordinates.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (e.g. 'Paris', 'Tokyo', 'New York')
latitudeNoLatitude of the location (e.g. 48.85 for Paris)
longitudeNoLongitude of the location (e.g. 2.35 for Paris)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that results are 'current' and read-oriented; it says nothing about units of measure, what fields come back, ambiguity handling for an unrecognized city, or what happens when the agent supplies both a city and coordinates. For a zero-annotation tool this leaves the agent guessing at invocation edge cases.

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?

Two short sentences with no filler, and the location-input constraint is placed immediately after the purpose statement so the agent can act on it right away.

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?

For a simple three-parameter read tool with no output schema, the definition covers purpose and input shape. It is incomplete in that no parameters are required in the schema, so the stated either/or rule needs an explicit fallback, and the absence of annotations means the agent gets no signal about return format or units.

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 the baseline would be 3, but the description adds a genuine mutual-exclusion constraint ('either a city name OR latitude+longitude') that the schema does not encode — nothing is marked required, so the schema alone would suggest all three could be passed together. That is real added meaning, though it still does not define the failure case when neither form is given.

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: 'Get current weather conditions for a location.' The word 'current' meaningfully scopes it away from forecast or historical data. It does not need to differentiate from the listed siblings, which are all document/GitHub/log utilities, so a 4 rather than a 5.

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?

The description tells the agent how to supply a location but gives no guidance on when this tool is the right choice versus anything else, and no exclusions. The either/or phrasing is really input-shape guidance, not usage routing.

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