Skip to main content
Glama
Sign In

Statuz

by app.statuz
OverviewDiscussionsAdmin

Check DM or reply reach

reach_check
Read-only

Whether a DM or a public reply from an account would reach someone. X: a DM is open when they take the account's DMs; a reply only when --post mentions or quotes the account. Bluesky: their chat settings, and the thread's reply limits. Mastodon: both open. LinkedIn and Reddit: no DMs. An account that signed in before Statuz asked for DMs says reconnect.

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": {
      "account": "<account>",
      "to": "<to>"
    },
    "name": "reach_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTheir handle
orgNoOrg id (default: your first org)
postNoTheir post a reply would answer
accountYesAccount id, handle or platform name (its default account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds real value by disclosing the platform-specific reach rules that drive the result. It also surfaces a state-dependent failure mode (accounts that predate the DM permission request return `reconnect`), which is behavior an agent could not infer elsewhere.

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 core purpose is front-loaded in one sentence, followed by a compact per-platform list that carries all the decision-relevant detail. The telegraphic fragments ('Mastodon: both open.') are dense but not padded; nothing reads as filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters, full schema coverage and no output schema, the description should say what the check returns (a boolean? a per-platform reason code?). It only hints at one return token (`reconnect`), so an agent knows the inputs but not the response shape.

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 the baseline is 3, and the description earns an upgrade by explaining that `post` matters only in that a reply reaches when the post mentions or quotes the account. The `to` handle and `account` selector are left to the schema, which already documents them.

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 first sentence states a specific check (reachability of a DM or reply from a given account) rather than a vague action, and the per-platform breakdown confirms the scope. It implicitly separates itself from dms_send/posts_create by being a read-only preflight check, but never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the conditions under which a DM or reply *would* reach per platform, which implies the tool is called before sending. However, it never states when to call this versus just calling dms_send or posts_create, nor any exclusions or preconditions order.

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