Smarter Weather Developer Onboarding

Get the Smarter Weather sign-up URL

sign_up

Read-onlyIdempotent

Returns the Smarter Weather developer sign-up URL (with MCP referral attribution). Present the URL so the user can create a free account in a browser (Clerk, no credit card). After they finish, reconnect this MCP server with OAuth and call create_api_key, then configure_mcp. No authentication required.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`widget`	No	sw-ui-spec widget block rendered by the MCP Apps onboarding widget (ui://onboarding-widget/v1/index.html). Additive; safe to ignore.
`signupUrl`	Yes
`instructions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedOutput schema / properties / widget / properties / entries / items / properties / props / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
First observedJul 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare readOnly, idempotent, non-destructive, and the description is fully consistent while adding value beyond them: the URL carries MCP referral attribution, the account is created with Clerk with no credit card, the flow happens externally in a browser, and the follow-up OAuth + create_api_key + configure_mcp chain is required afterwards. That is exactly the context an agent needs to handle the tool correctly.

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?

Three sentences, front-loaded with what is returned, then how to use it, then what to do next. Every sentence carries operational information; nothing is redundant with the title or annotations.

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?

An output schema exists, so return-value details are not needed in prose. For a zero-parameter, read-only URL fetch, the description covers purpose, usage, external-flow caveat, auth requirement, and the downstream sequence – nothing material is missing.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4. The description correctly implies no inputs are needed and focuses on what the returned URL is for, adding meaning without inventing parameters.

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?

States a specific verb ('Returns') and resource ('Smarter Weather developer sign-up URL'), plus a distinguishing detail (MCP referral attribution). It is clearly separable from siblings like get_plans or start_trial, which do not produce a sign-up URL.

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

Usage Guidelines5/5

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

Gives an explicit use case (present the URL so the user can create a free account in a browser) and a step-by-step follow-on sequence: reconnect with OAuth, then call create_api_key, then configure_mcp. It also states the precondition that no authentication is required. The only minor gap is not naming sibling alternatives by name, but the workflow makes selection unambiguous.

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

All Smarter Weather Developer Onboarding tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.