Smarter Weather

Find tools

find_tools

Read-onlyIdempotent

Lists the weather tools this connection does not show (best times, routes; storm cells, storm reports, lightning; outlooks, forecaster text; forecast accuracy; maps and charts), with when to use each and its required arguments. Run one with call_tool, in this session, no reconnect. With tools, returns their full input schemas. Free; no network call.

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

Input Schema

Name	Required	Description	Default
`tools`	No	Tool names: return their full input schemas instead of the list.

Output Schema

Name	Required	Description
`next`	Yes
`tools`	No	With `tools`: each named tool as tools/list would list it.
`toolsets`	No	The tools this connection does not list, by toolset.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / tools / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / toolsets / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / toolsets / items / properties / tools / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
AddedOct 24, 2026

TDQS

A3.9/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, so the safety profile is covered. The description adds genuinely new behavioral context: the call is free, makes no network call, requires no reconnect, and returns full input schemas when names are given. Only return-shape/pagination details are absent, and an output schema exists to cover those.

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 core purpose and the follow-up action are front-loaded in one tight paragraph with no filler. The parenthetical category list is long and slightly run-on, but it is substantive inventory rather than padding.

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

Completeness4/5

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

For a discovery tool with one optional parameter and an output schema, the description covers purpose, the two modes, cost/network behavior, and the next step. An agent has everything needed to call it and act on the result.

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% for the single optional `tools` parameter, and the schema description already states it returns full input schemas instead of the list. The description restates this without adding format, naming, or limit guidance, so the schema does the heavy lifting.

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 uses a specific verb and resource — it lists the weather tools this connection does not expose — and enumerates the categories covered (best times, storm cells, outlooks, forecast accuracy, maps). It implicitly distinguishes itself from call_tool, which is named as the way to run a discovered tool, though the phrasing 'tools this connection does not show' is slightly indirect.

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 tells the agent what to do after discovery ('Run one with call_tool, in this session, no reconnect') and clarifies the alternate mode when the `tools` argument is supplied. It does not state an explicit when-not condition, but the routing to call_tool is 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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.