Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_weather

Get real-time weather data for any city worldwide. Specify the city to receive current conditions.

Instructions

Real-time weather data for any city worldwide. Query param: ?city=Beijing

Price: unknown on Base (auto-paid in 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": "cn402_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It states the tool provides 'real-time weather data' and mentions a price, but does not disclose any behavioral traits such as read-only nature, rate limits, authentication needs, or side effects. The price note is vague and does not clarify cost implications.

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?

The description is brief with two sentences. The first sentence is informative about the tool's function. The second sentence about pricing is extra but not essential. No wasted words, though the structure could be improved by separating functional details from cost.

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?

Given the lack of output schema, no annotations, and a mismatch between description and input schema, the description is incomplete. It does not explain how to use the tool effectively, what the response format is, or how to handle the apparent parameter discrepancy. The price mention adds minimal context.

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?

The input schema has zero parameters, but the description introduces a query parameter 'city' without defining it in the schema. This inconsistency undermines the tool's usability. The description adds meaning but in a way that contradicts the structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Real-time weather data for any city worldwide,' which clearly indicates the tool's purpose. However, the mention of a query parameter '?city=Beijing' conflicts with the input schema that defines zero parameters, causing confusion and reducing clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus sibling tools like cn402_almanac or cn402_solar. The description does not mention any prerequisites, limitations, or context for appropriate use.

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