Skip to main content
Glama

Health of every account

accounts_get_all_accounts_health
Read-onlyIdempotent

Returns the status and last error of every account you can reach (only the broken ones with problems_only). Use it when calls fail or before a big job, to find accounts that need reconnecting (needs_reauth) or are paused; tell the user, because only the owner can reconnect. Example: { "problems_only": true }.

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

Input Schema

NameRequiredDescriptionDefault
profile_idNoOnly accounts in this profile (`prf_…` from profiles_list).
problems_onlyNoOnly accounts that are not active (needing reconnection, paused, failing).

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new context: the needs_reauth/paused states, that last error is returned, and the operational constraint that only the owner can reconnect — a real behavioral fact not in the schema.

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?

Front-loads the return content, then usage, then the example — a sensible order with little waste. The parenthetical about problems_only is slightly awkwardly placed mid-sentence but the whole thing stays compact.

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?

An output schema exists, so return values need not be spelled out, and the description still names the key fields (status, last error). Combined with the owner-reconnect caveat, an agent has enough to call and act on results; only sibling differentiation is missing.

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%, so both parameters are already documented, and the description's gloss on problems_only ('only the broken ones') largely restates the schema. The example call adds a small amount of practical value but no new semantics for profile_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns status and last error for every reachable account, with an explicit scope modifier for problems_only. It is clear what the tool does, though it never names accounts_list or accounts_get to sharpen the boundary against those siblings.

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 concrete triggers ('when calls fail or before a big job') and the goal (find accounts needing reconnection or paused), plus a follow-up instruction to tell the user. It stops short of naming an alternative tool for the non-health listing case, so it is strong but not fully routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources