Skip to main content
Glama

AutoTasker Hub — China Social Data API

open_meteo_marine

Marine conditions: wave height, sea surface temperature, swell for coastal coordinates. $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": "open_meteo_marine"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
cityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden, and it only adds the $0.01 USDC cost — genuinely useful, since it warns of a paid call. It does not say how payment/authentication works, whether requests are rate-limited, what units the values are in, or over what time horizon the data applies.

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?

Two short, front-loaded sentences with the payload description first and the price second; nothing is redundant. It is efficient, though the brevity is partly a symptom of missing information rather than disciplined compression.

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?

A three-parameter, no-annotations, no-output-schema tool needs the description to resolve input ambiguity and return semantics, and this one leaves the lat/lon-versus-city choice unresolved and units unspecified. For a paid data endpoint, that is a substantial gap an agent cannot fill from structured fields.

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?

Schema description coverage is 0% and all three parameters are undocumented, so the description must compensate but barely does. 'Coastal coordinates' hints that lat/lon are the intended inputs, yet it never explains the city parameter, whether city overrides coordinates, or what format a city name takes — critical since zero parameters are required.

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 concrete resource domain — marine conditions — and enumerates the returned variables (wave height, sea surface temperature, swell) plus the target geography (coastal coordinates), which separates it from land-based or general-weather siblings such as air_quality. It stops short of an explicit verb or a named alternative, but an agent can tell what it fetches.

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?

There is no guidance on when to prefer this tool, no prerequisites, and no exclusions. The only usage-adjacent signal is the price line, which tells the agent a charge applies but not when charging it is warranted. Nothing says whether it should be used only for coastal points or what to do for inland locations.

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.