Skip to main content
Glama
Sign In

Smarter Weather

by io.github.smarterweather
OverviewDiscussionsAdmin

Call tool

call_tool
Read-onlyIdempotent

Runs a tool find_tools lists, by name: same price, limits and result as calling it directly. Tools already in your list are called directly, not through this. arguments follows that tool's input schema.

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": {
      "tool": "<tool>"
    },
    "name": "call_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool name, from find_tools.
argumentsNoThat tool's arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the safe annotations (readOnly, idempotent), the description adds crucial operational behavior by stating it runs the tool with 'same price, limits and result' as a direct call. This provides the agent with essential execution context.

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 brief, using only two sentences. It prioritizes the core mechanism and the exclusion criteria immediately, demonstrating excellent structure.

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?

Given that the wrapper's function is primarily routing, the description covers the high-level usage requirements well. It clarifies the execution mechanism and its bounds. A score of 4 reflects that while usage is clear, specific error handling or input validation details (beyond the schema) are not present.

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 coverage is 100%, so the schema already defines the parameters. The description primarily functions to reinforce that the `tool` parameter must be sourced from the `find_tools` list, which is a necessary piece of context but doesn't add functional semantic meaning beyond the schema.

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 purpose is highly specific: it runs a tool, but critically, it defines *how* it runs it (via the list generated by find_tools, matching price/limits). It also explicitly differentiates itself from standard direct calls for tools already in the user's list.

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 provides clear guidance on when *not* to use the tool: when the tool is already in the list, it should be called directly. This defines a specific operational constraint necessary for usage.

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

All Smarter Weather toolsInspect
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.

Resources