Skip to main content
Glama
Sign In

glimind

by io.github.shawndei
OverviewDiscussionsAdmin

call_remote_tool

Destructive

WHEN TO CALL: to run a tool on another remote MCP server without connecting to it or loading its tool list. Pass server (id or short name), tool and arguments; returns that tool's result. Works for live servers that need no login; for others it answers needs_auth or not_callable with how to connect directly. Never send secrets in arguments. Needs a free key: create_key mints one (100 calls a day) in one call, then pass it as apiKey.

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_remote_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe tool's name on that server (or a full id 'server/tool').
apiKeyNoOptional Glimind key (from create_key) if your MCP connection has none. Never forwarded.
serverNoThe server id or short name (from find_tool or route_task).
argumentsNoThe tool's arguments, matching its input schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / apiKey
      Added value: +{
+  "description": "Optional Glimind key (from create_key) if your MCP connection has none. Never forwarded.",
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

The description adds real context beyond the annotations. It names the needs_auth and not_callable failure responses, the key requirement and the 100 calls a day rate limit, and it warns never to send secrets. It does not explain why destructiveHint is true, i.e. that the remote tool's side effects are arbitrary, but nothing contradicts the annotations.

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?

It is dense and front-loaded with the when-to-call statement, and every sentence carries information. The phrasing is somewhat telegraphic, but there is no waste.

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 no output schema, it says the result is the remote tool's result or a needs_auth/not_callable answer with connection guidance. For a proxy tool with nested arguments this is fairly complete. It is missing only error and timeout behavior and the side-effect caveat.

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%. The description restates server/tool/arguments and adds that apiKey comes from create_key, which the schema already says. This is a baseline contribution with little new meaning.

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 description states the action precisely: run a tool on another remote MCP server without connecting to it or loading its tool list. That is clearly distinct from siblings like find_tool, route_task and prepare_tool_call, which discover or plan rather than execute.

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 opens with an explicit 'WHEN TO CALL' clause and limits scope to live servers that need no login. It also names create_key as the prerequisite. It does not say whether to use prepare_tool_call or preflight_tools first, although the schema mentions find_tool and route_task as sources for server.

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

All glimind 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