Skip to main content
Glama

AutoTasker Hub — China Social Data API

weather

Current weather via Open-Meteo (city or lat/lon). $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
cityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does add genuinely useful context beyond the schema by disclosing the upstream provider and the paid cost ($0.01 USDC), but it leaves the response shape, units, and error/default behavior unstated.

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 fragments, zero filler, and the resource is front-loaded ahead of the input modes and the price. Every clause carries information an agent needs.

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 three-parameter tool with no annotations and no output schema, the description covers what the tool returns and how to address it, but not the notable edge case that zero parameters are required — an agent cannot tell whether calling with no arguments is valid or an error, or how city versus coordinates resolve.

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 0%, so the description must compensate. It does add the key semantic that 'city' and 'lat/lon' are alternative addressing modes, but it omits whether lat+lon must be paired, which takes precedence when both are supplied, and what a valid city string looks like. Partial compensation for the coverage gap.

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 names a specific resource ('current weather') and a specific data source ('Open-Meteo'), which tells an agent exactly what it will get. It does not distinguish itself explicitly from weather-adjacent siblings like air_quality, but the resource term is precise enough to select on.

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 implied rather than stated: 'current' signals this is not a forecast tool, and the parenthetical signals two input modes. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to alternatives for related needs such as air quality.

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.