AccountHub

get_chat_setup_status

Read-only

AccountHub shared project and direct chat setup status for yourself: which setup steps are your turn, which are waiting (on an admin, on ChatGPT, or on AccountHub's own check, with the deadline), postponed or done, and how new chat messages will reach you (deliver now / scheduled task / email-Slack). Facts only, read only. The setup steps themselves ("done", "it was shown", "stopped") are the person's own reports in the AccountHub chat screen — never press or claim them on the person's behalf; send them to /chat?setup=1 instead.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The readOnlyHint already marks this as a safe read, and the description adds important behavioral context beyond annotations: statuses are facts only and the setup-step reports are the person's own claims, which the agent must not assert for them. This materially guides correct agent 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 front-loaded with the resource and self scope, then adds the critical behavioral warning. It is dense but every part is relevant; the parenthetical lists make it slightly heavy, but there is no clear waste.

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?

With no required parameters and no output schema, the description adequately explains what status categories are returned and how delivery modes are represented. It also covers the key constraint about not impersonating the person's setup-step claims.

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?

The tool takes zero parameters, so there is no parameter semantics gap for the description to fill. The description appropriately focuses on scope and return categories rather than parameter details.

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 resource and scope: AccountHub shared project and direct chat setup status for the caller, including which steps are theirs, waiting, postponed, done, and how messages arrive. It is clear and distinct, though it does not explicitly name a sibling tool for comparison.

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 strong usage constraint: setup-step reports belong to the person and must not be pressed or claimed on their behalf; instead the agent should send them to /chat?setup=1. It does not explicitly compare against nearby list/status siblings, but the when-not guidance is clear.

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

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