Statuz

Connect account

accounts_connect

Connect an account by signing in with the platform in your browser. Locally the sign-in returns to 127.0.0.1:3851 and the tokens go into the OS keychain. X and LinkedIn use your own developer app: set its keys first with statuz config set x.client-id … (see statuz help config). Bluesky and Mastodon need nothing.

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": {
      "platform": "<platform>"
    },
    "name": "accounts_connect"
  }
}

Input Schema

Name	Required	Description
`org`	No	Org id (default: your first org)
`server`	No	Mastodon instance (mastodon.social) or your Bluesky handle, for a custom server
`browser`	No	Open the browser (--no-browser prints the link)
`platform`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already flag openWorldHint=true, idempotentHint=false, and destructiveHint=false; the description adds real context beyond that — the localhost:3851 callback, token storage in the OS keychain, and per-platform credential prerequisites. It omits whether reconnecting replaces an existing token and what the flow returns on success.

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?

Three front-loaded sentences, each carrying distinct information — action, local mechanics, and per-platform prerequisites. The inline config command is dense but directly actionable, with no filler.

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?

For an interactive, side-effecting auth tool with no output schema, the description covers the flow, storage location, and setup prerequisites well. The missing piece is what the caller gets back (account id, success flag) and whether the call blocks waiting for the browser.

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?

At 75% schema coverage the baseline is 3, and the description earns that by explaining the `server` parameter implicitly (Mastodon instance / Bluesky handle) and the browser flow. But the `platform` enum includes "reddit," which the per-platform guidance never addresses, and `org` is never mentioned.

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+resource ("Connect an account") and the mechanism (browser sign-in routed through a local callback into the OS keychain). It does not, however, distinguish itself from the sibling cloud_accounts_connect, which an agent could easily confuse it with.

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 per-platform conditions: X and LinkedIn require pre-registered developer app keys via `statuz config set x.client-id`, while Bluesky and Mastodon need no setup. It lacks an explicit statement of when to prefer this over cloud_accounts_connect or accounts_check, so it stops short of the 5 bar.

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

All Statuz 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?