Skip to main content
Glama

compare_weather

Read-only

Compare current weather across multiple locations.

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": {
      "locations": "<locations>"
    },
    "name": "compare_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without the description. Beyond that the description adds nothing: no indication of how many locations are practical, whether results are side-by-side or a summary, or any open-world/latency behavior implied by querying external weather sources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no padding — the intent lands immediately. The trade-off is that the brevity comes at the cost of any parameter or behavioral guidance, so it is tight but thin rather than genuinely well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but the sole input parameter is an opaque array of objects with no documentation anywhere. For a tool whose only input shape is unspecified, the description should clarify the location object contract; it does not.

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

Parameters2/5

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

There is a single required parameter, 'locations', defined as an array of free-form objects with additionalProperties=true and 0% schema description coverage. The description does not say what fields each location object should carry (name? coordinates? id?) or whether geocoding is required first, leaving the only parameter effectively undocumented.

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?

The description gives a specific verb ('Compare') and resource ('current weather') with scope ('across multiple locations'), which implicitly separates it from the single-location get_current_weather sibling. It stops short of naming any sibling explicitly, but an agent can still infer the distinction.

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 'multiple locations' — the agent can reason that this is the choice when several places must be compared at once. There is no explicit when-to-use, when-not-to-use, or named alternative such as get_current_weather for a single site.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.