OpenWeather for agents

Sign up

sign_up

Creates a Forum account for an email address under the Terms version currently served, and returns the account, its secret — the one string that runs the account, shown exactly once — its first data key, shown exactly once, and the 1,000-credit signup grant spendable on any product. The result's configure block is the client configuration entry that sends the data key from then on; until the client reconnects, pass data_key.key as data_key on fetch_data. Keep the secret with the owner and pass it as secret on account_status and get_topup_link. An address that already has an account answers 409 email_exists with next_action login_to_link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	Yes	the owner's email address — the account's identity; one account per address

Output Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No
`fault`	No
`usage`	No
`record`	No
`status`	No
`account`	No
`headers`	No
`upstream`	No
`body_text`	No
`configure`	No
`transport`	No
`key_source`	No
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical one-time-only behaviors: the secret is shown exactly once, the first data key is shown exactly once, and the 1,000-credit grant is included. It also explains how to use the returned configure block for fetch_data and how to pass secret on account_status and get_topup_link. The 409 error response and next_action are also described.

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 dense but well-structured, with every sentence serving a distinct purpose: what is created, what is returned, how to use the returned artifacts, and what happens on duplicate signup. There is no filler or repetition.

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

Completeness5/5

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

The description covers the full lifecycle: creation, returned credentials, immediate follow-up usage on fetch_data, account_status, and get_topup_link, plus the duplicate-account error path. Given that an output schema exists, nothing important for an agent to call this tool correctly is missing.

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?

The schema already fully documents the email parameter with 100% coverage, including that it is the account identity and one account per address. The description reinforces this and adds context about the 409 behavior, but it does not materially add parameter semantics beyond what the schema already states.

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 and resource: 'Creates a Forum account for an email address.' It clearly distinguishes sign_up from its siblings, which all manage or query existing accounts rather than creating them. The behavior is concrete and unique.

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

Usage Guidelines4/5

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

The description implies when to use sign_up: to create a new Forum account for an email address. It also provides a clear conditional: existing accounts return 409 email_exists with next_action login_to_link, steering the agent away from re-signing up. However, it does not explicitly state general alternatives like 'use account_status to check an existing account.'

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

All OpenWeather for agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a single unambiguous role: catalogue browsing, data fetching, account creation, account status, and top-up. Even get_product and list_products are cleanly separated by singular/plural and detail level.

Naming Consistency4/5

Most tools follow a verb_noun pattern (fetch_data, get_product, get_topup_link, list_products), and all names are lowercase snake_case. account_status and sign_up break the verb_noun pattern, but they are still readable and predictable.

Tool Count5/5

Six tools is a well-scoped set for an API platform server: discovery, data access, account monitoring, and top-up each have dedicated coverage. No tool feels redundant, and the count is appropriate for the server's purpose.

Completeness4/5

The set covers the full usage loop: sign up, discover products, fetch data, check balance/usage, and top up. Minor gaps exist — sign_up references a login_to_link action that no tool provides, and there is no key rotation or management — but they do not block the primary agent workflow.

Resources

Need Help?