Skip to main content
Glama

Call a tool on a proxied MCP server

proxy_call

Invoke a tool on an external MCP server using server__tool addressing, allowing agents to call discovered tools directly.

Instructions

Invoke a tool on an external MCP server that this server proxies, addressed as server__tool. Not covered by proxy_discover, which lists the tools without calling 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": {
      "tool": "<tool>"
    },
    "name": "proxy_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool name in server__tool form.
argumentsNoArguments for the call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the important context that execution happens on an external, outside-this-server target, reinforcing open-world side effects, but says nothing about failure modes, remote errors, or whether arguments are validated or passed through raw.

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?

Two short sentences, zero filler, with the core action and addressing form front-loaded and the sibling disambiguation trailing it. Every clause carries information.

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?

There is no output schema, so the description would ideally indicate what a call returns (the remote tool's result, or an error object on failure), and it is silent on that. For an open-world passthrough tool with a nested free-form arguments object, this leaves a meaningful gap despite otherwise adequate coverage.

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%, so the schema already documents both parameters, and the server__tool form is stated in both places with no added syntax detail. The description gives no guidance on the free-form 'arguments' object, which is opaque and would benefit from a note that it must match the target tool's 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?

States a specific verb (invoke) plus the exact resource (a tool on a proxied external MCP server) and the addressing convention (server__tool). It explicitly distinguishes itself from proxy_discover, so an agent can pick between them without opening either schema.

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 contrasts with proxy_discover: that tool lists tools, this one calls them. That is a clear selecting condition, but the description never states prerequisites such as needing a tool name obtained from proxy_discover first, nor any limits on which servers may be called.

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