Skip to main content
Glama
Sign In

Smarter Weather Developer Onboarding

by io.github.smarterweather
OverviewDiscussionsAdmin

Start a Smarter Weather trial API key

start_trial

Does not mint from the hosted server. Prefer npx -y @smarterweather/mcp-onboarding@latest trial (no MCP host), or add the stdio bridge and call start_trial there. Both write SMARTERWEATHER_API_KEY to .env and never print the bearer. If you already run the package and still see this, restart it on @latest.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: it does not mint from the hosted server, the alternatives write SMARTERWEATHER_API_KEY to .env, and the bearer is never printed. That adds meaningful operational context about side effects and secret handling.

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 text is compact and every sentence carries relevant onboarding or secret-handling information. It could be slightly more front-loaded by stating the tool's actual behavior before the limitations, but there is little waste.

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 no-parameter onboarding tool with no output schema, the description should make clear what the caller experiences when invoking start_trial. It gives useful migration and secret-handling context, but it does not fully explain the invocation result or why this MCP tool exists if the preferred path is external.

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 zero parameters, so there is no parameter-level ambiguity for the description to resolve. The baseline for a no-parameter tool is 4.

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 signals a trial-key setup context, but it never plainly states what calling start_trial itself does. It mainly explains that this tool does not mint from the hosted server and points to alternatives, leaving the actual operation partly implicit.

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?

It clearly prefers the standalone `npx -y @smarterweather/mcp-onboarding@latest trial` path and gives an alternative via the stdio bridge. It also tells the agent to restart on @latest if the package is already running, though it does not explicitly say when calling this tool is appropriate.

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 toolsInspect
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.

Resources