Skip to main content
Glama

call_tool

Invoke any tool on the runelay MCP server by its full source.tool name with arguments. Use it to reach shared agent tools, accounts, and memory from one endpoint without extra logins.

Instructions

Call one tool by its full name (source.tool) with arguments.

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

Input Schema

NameRequiredDescriptionDefault
argsNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it says nothing about side effects, whether the target tool's own safety profile governs behavior, what happens when the named tool does not exist, or how errors surface. The only added behavioral detail is the 'source.tool' naming convention.

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?

A single front-loaded sentence with the key constraint (full name, source.tool) in parentheses. Zero filler.

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

Completeness2/5

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

For a meta-invocation tool with a free-form nested 'args' object, no annotations, and no output schema, the description leaves important gaps: how results and errors are returned, whether the call is proxied/executed directly, and whether 'args' can be omitted for zero-argument tools.

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 description coverage is 0%, so the description must compensate. It does explain that 'name' is a fully qualified source.tool string and that arguments are passed through, but it never says that 'args' must conform to the target tool's own schema or that 'args' is optional.

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?

States a specific verb and resource ('Call one tool by its full name') and clarifies the required name format as 'source.tool'. This is unambiguous about what the tool does, though it does not contrast itself with plausible siblings like search_tools or execute.

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

Usage Guidelines2/5

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

The description gives no guidance on when to prefer this generic invoker over a direct/specific tool call, nor any prerequisite such as discovering the tool name via search_tools first. Usage is only implied by the name format.

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