Prubex

Overview of your Prubex access

prubex_overview

Read-onlyIdempotent

Call this first. Returns what this server can do for you: the current time and default time zone, your scopes and whether your key holds every send for approval (account policies can hold more), the accounts you can reach by provider, any that need the owner to reconnect, and links. Use it at the start of a session and whenever calls start failing. Example: {}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prubex_overview"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`now`	Yes	The current time, ISO 8601 with offset in `time_zone`.
`links`	Yes
`accounts`	Yes
`principal`	Yes
`time_zone`	Yes	The workspace time zone, the default for calendar tools.
`workspace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by listing the diagnostic information returned, including scopes, approval-hold status, account reachability, and reconnect needs.

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 front-loaded with "Call this first" and then efficiently lists what the tool returns. Every sentence contributes either invocation guidance or return-content context, with no wasted text.

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?

An output schema exists, so the description need not explain return values in detail. For a zero-parameter overview tool with full annotations, the description provides enough context about when to call it and what it covers.

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?

The tool has zero parameters, so the baseline is 4. The description reinforces this with "Example: {}", making it clear that no arguments are required.

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 purpose: an overview that returns server capabilities, time zone, scopes, approval status, reachable accounts, reconnect needs, and links. It clearly distinguishes itself as the first-call diagnostic tool rather than a resource-specific sibling like accounts_list or mail_list_messages.

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 gives explicit usage timing: "Call this first" and "Use it at the start of a session and whenever calls start failing." It does not name alternatives or when-not conditions, but the first-call and failure-recovery guidance is clear and actionable.

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?