Prubex

List connected accounts

accounts_list

Read-onlyIdempotent

Lists the email and calendar accounts you can reach, with each one's account_id, provider, address, profile, status and capabilities. Use it first when a write needs account_id, or to see which accounts can do something (filter by capability). Example: { "capability": "mail.send" }.

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": "accounts_list"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Results per page, 1–100 (default 20).
`cursor`	No	The `next_cursor` from the previous page. Omit for the first page.
`status`	No	Only accounts in this state.
`provider`	No	Only this provider (iCloud, Yahoo and others are "imap").
`capability`	No	Only accounts that can do this, e.g. "mail.send". "calendar.free_busy" is the account's own availability; "calendar.attendee_free_busy" is looking up other people's.
`profile_id`	No	Only accounts in this profile (`prf_…` from profiles_list).

Output Schema

Name	Required	Description	Default
`items`	Yes
`next_cursor`	No	Pass as `cursor` for the next page; absent on the last page.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context beyond that: the exact field set returned and the semantic distinction between calendar.free_busy (own availability) and calendar.attendee_free_busy (others'), which prevents a real misuse.

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 sentences plus a compact example, with the primary use case front-loaded and zero filler. Every clause carries information an agent needs.

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 return values need not be spelled out, yet the description still names the key fields. For a read-only, zero-required-parameter list tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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 baseline is 3; the description goes beyond by showing the capability filter in action ('Example: { "capability": "mail.send" }') and framing account_id as the value writes require. It does not add anything for limit/cursor/status/provider beyond the 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 and resource ('Lists the email and calendar accounts you can reach') and enumerates the returned fields (account_id, provider, address, profile, status, capabilities). This clearly separates it from accounts_get (single account) and accounts_get_all_accounts_health (health view).

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?

Gives two concrete triggers: 'Use it first when a write needs account_id' and 'to see which accounts can do something (filter by capability)', plus a worked example. It does not explicitly name the sibling to use instead for a single-account lookup, so it stops short of full when/when-not routing.

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?