Skip to main content
Glama
Sign In

Smarter Weather Developer Onboarding

by io.github.smarterweather
OverviewDiscussionsAdmin

Search Smarter Weather documentation

get_documentation
Read-onlyIdempotent

Search the Smarter Weather developer documentation index (quickstart, REST API, MCP server, errors, rate limits, SDKs, pricing, API keys). Returns up to 5 matching entries with title, URL, and an actionable summary. No authentication required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "get_documentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms, e.g. "authenticate rest api" (max 200 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description adds genuinely useful context beyond that: the result cap (up to 5 entries), the fields returned (title, URL, summary), and that no authentication is required.

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?

Two sentences, zero filler: scope and topics come first, then return shape and auth requirement. Every clause earns its place.

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?

For a single-parameter, read-only search tool with no output schema, the description supplies the missing return-shape information (count cap and fields), the domain of the index, and the auth posture. Nothing needed to invoke it correctly is absent.

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?

Schema coverage is 100% and the single query parameter already has a description plus an example and a 200-char limit. The description restates the concept of search terms but adds nothing about phrasing, matching behavior, or handling of broad vs. narrow queries, so baseline 3 is appropriate.

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 (search) and resource (the Smarter Weather developer documentation index) and enumerates the covered topic areas. This is clearly distinguishable from siblings like get_plans or sign_up, which are about plans and account actions rather than docs.

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 makes the use case clear: consult it for developer documentation questions. However, it never explicitly frames when to prefer it over siblings or what to do when results are insufficient; usage is clear by implication rather than stated.

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