mcp-www

call_remote_tool

Execute any tool on a remote MCP server. First browse to discover available tools, then call them by providing the URL, tool name, and arguments.

Instructions

Call a tool on a remote MCP server. Use browse first to discover available tools, then use this to execute them.

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

Input Schema

Name	Required	Description
`url`	Yes	The MCP server URL (e.g., 'https://mcp.example.com')
`tool`	Yes	The name of the tool to call on the remote server
`arguments`	No	Arguments to pass to the remote tool

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 10, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It reveals the execution nature of the tool but lacks disclosure of potential risks (e.g., executing arbitrary remote tools), authentication requirements, error handling, or side effects.

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 a concise two-sentence structure that front-loads the action and provides a clear sequential instruction. No unnecessary wording.

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?

Covers the core purpose and usage sequence but omits important context such as return format, error handling, and security considerations. Given that this is a remote execution tool, these gaps are more significant.

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 100%, with each parameter (url, tool, arguments) having a description. The tool description adds no additional parameter-specific meaning beyond what the schema already provides.

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?

Clearly states it calls a tool on a remote MCP server. The verb 'call' and resource 'remote MCP server' are specific, and the description distinguishes from sibling discovery tools like browse and discover.

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?

Explicitly instructs to use browse first for discovery, providing a clear usage sequence. However, it does not mention when not to use this tool or alternatives for other operations like reading resources.

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

Deploy Server