Skip to main content
Glama
Sign In

Statuz

by app.statuz
OverviewDiscussionsAdmin

Start account sign-in

cloud_accounts_connect

Start connecting an account to Statuz Cloud: returns a sign-in link to open. Open the link in a browser, then wait with cloud.accounts.connected. statuz accounts connect does both for you. Cloud signs in with Statuz’s own X and LinkedIn apps: no developer keys.

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

Input Schema

NameRequiredDescriptionDefault
orgNoOrg id (default: your first org)
serverNoMastodon instance or your Bluesky handle, for a custom server
platformYes
returnToNoOperators acting in a tenant: where the browser goes when it ends, with ?connect=<connectId>&status=connected|failed[&error=<code>]; its origin must be in returnOrigins

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?

The description adds useful behavior beyond the annotations: it returns a sign-in link, requires browser interaction, and must be followed by polling cloud.accounts.connected. It also notes the absence of developer-key requirements. It doesn't mention link expiration or that repeated calls likely create new connect sessions, which would have been valuable given non-idempotent behavior.

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 description is three tight sentences, front-loading the core action and return value before the follow-up step. The final sentence about Statuz's own X and LinkedIn apps is relevant context but slightly less essential.

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?

No output schema exists, so the description's explanation of the return value (a sign-in link) and the subsequent polling step is crucial and adequately covers the core flow. The remaining param-specific details (server, returnTo) are left to the schema, which is reasonable at 75% coverage.

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 75%, with descriptions for org, server, and returnTo. The description does not explain any parameters beyond what the schema provides, and the platform parameter itself lacks a schema description (though the enum values are self-explanatory). Baseline 3 is appropriate.

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?

The description states a specific verb and resource ('Start connecting an account to Statuz Cloud') and clarifies the immediate output ('returns a sign-in link to open'). It also names the follow-up tool (cloud.accounts.connected), which helps distinguish it from siblings, though the presence of an 'accounts_connect' sibling leaves slight room for confusion.

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 a clear workflow: open the returned link in a browser, then wait with cloud.accounts.connected, and notes the CLI command does both steps. This is strong operational guidance, but it doesn't explicitly state when not to use this tool (e.g., if the account is already connected).

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

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