Skip to main content
Glama

weather_now

Read-only

Fetches current weather in Norway for a spoken place name and returns a short sentence to read aloud; omit the place for home conditions.

Instructions

The weather right now. 'place' is a place in Norway as the owner said it, such as 'Bergen' or 'Moen i Agder'; omit it for home. Data from MET Norway and Kartverket.

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": "weather_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value beyond that by naming the upstream data sources (MET Norway, Kartverket) and disclosing the implicit home-location default when 'place' is omitted; it stops short of units or freshness/latency details.

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?

Three short sentences, front-loaded with the purpose, then parameter meaning, then provenance. Nothing is redundant and nothing needs trimming.

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?

For a one-parameter read tool with an output schema, the description covers purpose, geography, input format, and default behavior adequately. Only minor operational details such as units or data freshness are left unstated, which the output schema likely absorbs.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does so well: it explains that 'place' is a free-text Norwegian place name as the owner would say it, gives two illustrative values including a multi-word one, and defines the omit-for-home default for the single optional parameter.

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 resource and temporal scope ('The weather right now'), which tells an agent exactly what it returns. There are no siblings to differentiate against, so the only missing element is a stronger verb phrasing such as 'Get current weather'.

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?

Gives clear operating context: places are in Norway only, and omitting 'place' returns home weather. No alternatives exist to route to, so the only gap is the absence of explicit when-not-to-use framing.

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

Deploy Server

Other Tools