Skip to main content
Glama
Sign In
open-meteo-mcp-lite

open-meteo-mcp-lite

by ominiverdi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_default_location

Retrieve the default location currently set for weather queries. Check which city or coordinates are configured as the default.

Instructions

Get the currently configured default location

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing any behavioral details like return format, error handling when no default location is configured, or whether it requires prior setup. The description does not say what the tool returns or what 'default location' means in practice.

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?

The description is a single, concise sentence that immediately states the tool's purpose without any filler. It is front-loaded and contains exactly the necessary information for a simple getter.

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 zero-parameter tool, the description is largely complete, but since there is no output schema, it does not specify the format of the returned location (e.g., string, object, lat/long). This leaves some ambiguity about how the output can be used with sibling tools like get_weather, which may require a location format.

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?

The tool has zero parameters, so the description does not need to explain parameter meanings. The schema already covers everything trivially, and the empty parameter list is self-explanatory. The description adds no parameter information because none exist.

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?

The description 'Get the currently configured default location' uses a specific verb ('Get') and a clear resource ('default location'), distinguishing it from sibling tools like set_default_location (mutates) and search_location (searches arbitrary locations).

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 gives a clear purpose but does not explicitly state when to use this tool versus alternatives such as search_location for finding locations or get_weather for weather data. Usage is implied rather than explicitly scoped.

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