Prubex

Run a tool found by search_tools

call_tool

Destructive

Runs a Prubex tool that is not in tools/list (find it with search_tools), with the same validation, permissions and approvals as calling it directly. Tools in tools/list must be called directly. Use it for the long tail: drafts, labels, folders, profiles, policies, agenda. Example: { "name": "mail_list_drafts", "arguments": { "account_id": "acc_…" } }.

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

Name	Required	Description	Default
`name`	Yes	The tool name from search_tools.
`arguments`	No	The tool's input.

Output Schema

Name	Required	Description	Default
`name`	Yes
`result`	Yes	The tool's own structured result.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already disclose destructiveHint=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=false. The description adds important behavioral context by stating that execution has the same validation, permissions, and approvals as calling the tool directly, which materially helps an agent understand the safety model.

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?

The purpose is front-loaded in the first sentence, and the description is appropriately compact for a meta-tool. The example adds practical value, though the long-tail category list is somewhat enumerative rather than essential.

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

Completeness5/5

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

Given the meta-tool complexity, open-world behavior, available output schema, and annotation coverage, the description supplies the critical missing context: discovery via search_tools, the direct-call boundary, and equivalence to direct invocation. An agent has enough information to decide when and how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by giving a concrete example showing that name is the target tool and arguments is the target tool's input object, which is especially helpful because the arguments property defines no fixed sub-properties.

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 a specific verb and resource: it runs a Prubex tool that is not in tools/list. It clearly distinguishes this meta-tool from directly listed tools and from search_tools, so an agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says to find the target tool with search_tools, that tools in tools/list must be called directly, and that this tool is for the long tail such as drafts, labels, folders, profiles, policies, and agenda. This gives clear when-to-use and when-not-to-use guidance with the relevant alternative named.

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

All Prubex tools Inspect

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

Need Help?