Skip to main content
Glama

Typebar (formerly SuperDocs)

get_account_status

Check your Typebar account status: tier, monthly operations used/remaining, and (for agent accounts) whether a human has adopted it.

Call this with your sk_ key. Useful before doing work (to confirm you have operations left) and before signing up again (to reuse your account).

Nearing your monthly cap and need to keep going? Hand the account to a human: POST /v1/agents/handoff with their email returns a one-time takeover code to give them; they open the emailed link, enter the code, and adopt the account in place (your work and this API key keep working) so they can upgrade and pay. No human? POST /v1/agents/request-upgrade instead. Full flow: https://docs.superdocs.app/introduction/agent-signup

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
hintNo
tierYes
quotaYes
adoptedNoFor agent accounts: whether a human has adopted it yet. Null for regular accounts.
account_idYes
is_agent_accountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description does carry the full burden, and it does disclose the auth requirement ('Call this with your `sk_` key') plus the fact that the account's work and key survive adoption. But it never states that this is a non-mutating read or whether calling it consumes quota, and roughly half the text describes external POST endpoints (/v1/agents/handoff, /v1/agents/request-upgrade) rather than this tool's own behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and use cases are correctly front-loaded in the first two sentences, but the remaining two-thirds is an escalation playbook (handoff email flow, takeover code, request-upgrade, docs URL) that belongs in a different tool's description and buries the core contract of a simple status check.

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?

The tool has an output schema, so return values need not be explained, and with no input parameters the only real gap is how the key is presented — which the description covers. It is complete enough to call, though the off-topic adoption narrative adds noise rather than missing information.

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?

Zero parameters, so the baseline is 4. The description adds the one piece of invocation context the empty schema cannot convey: the call must be made with the account's `sk_` key.

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

Purpose5/5

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

The first sentence names a specific verb and resource ('Check your Typebar account status') and enumerates the exact data returned: tier, monthly operations used/remaining, and human-adoption state for agent accounts. No sibling exposes account/tier/quota state, so the tool is trivially separable from the document, job, and session tools in the list.

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

Usage Guidelines5/5

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

It states two concrete use moments: 'before doing work (to confirm you have operations left)' and 'before signing up again (to reuse your account)'. It also routes the agent onward when this tool reveals an exhausted quota, naming the handoff and request-upgrade paths rather than leaving the next step to inference.

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.