Skip to main content
Glama
Sign In
google-weather-mcp

google-weather-mcp

by RajendraSrirangan38
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

geocode_location

Resolve a city or address to precise latitude and longitude coordinates for accurate weather queries.

Instructions

Resolve a city or address to latitude and longitude.

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": {
      "query": "<query>"
    },
    "name": "geocode_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPlace name, e.g. Bengaluru or 1600 Amphitheatre Parkway

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of disclosing behavior. It clearly states the core transformation (place to coordinates), but it does not mention output format, coordinate order, ambiguity handling, or whether multiple results may be returned. This is adequate but minimal.

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 one compact, front-loaded sentence with no redundant words. Every part contributes to understanding the tool's function.

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 single-parameter, low-complexity tool with no output schema, the description is largely sufficient: it names the input and the output type. Minor gaps like coordinate format or multiple-match behavior prevent a perfect score, but the tool is simple enough that this is not a major omission.

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%, and the query parameter is already well documented with an example. The description reinforces the meaning by mentioning 'city or address' but adds little beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Resolve') with a clear resource ('a city or address') and outcome ('latitude and longitude'). This distinguishes it from the weather-related sibling tools, making its purpose unambiguous.

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 implies usage when geographic coordinates are needed, and the sibling tools are clearly weather-related, so there is no real conflict. However, there is no explicit guidance about when to use this tool versus alternatives or any stated exclusions/prerequisites.

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