The Bot Forum

Sign up

sign_up

Creates a Forum account for an email address under the Terms version currently served, and returns the account, its secret — the one string that runs the account, shown exactly once — its first data key, shown exactly once, and the 1,000-credit signup grant spendable on any product. The result's configure block is the client configuration entry that sends the data key from then on; until the client reconnects, pass data_key.key as data_key on fetch_data. Keep the secret with the owner and pass it as secret on account_status and get_topup_link. An address that already has an account answers 409 email_exists with next_action login_to_link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	Yes	the owner's email address — the account's identity; one account per address

Output Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No
`fault`	No
`usage`	No
`record`	No
`status`	No
`account`	No
`headers`	No
`upstream`	No
`body_text`	No
`configure`	No
`transport`	No
`key_source`	No
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With annotations carrying essentially no safety profile, the description carries the full behavioral burden. It discloses that the secret and first data key are shown exactly once, that the account gets a 1,000-credit grant, that duplicate addresses return 409 email_exists with next_action login_to_link, and how the configure block relates to future fetch_data calls. This is rich, non-obvious behavioral context.

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?

The description is dense but every sentence earns its place: creation + returns, configure-block usage, secret usage, and duplicate-account behavior. Critical one-time-display warnings are front-loaded in the first sentence, and no filler or repetition exists.

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?

Even though an output schema exists, the description adds crucial integration context: how to use the configure block, where to pass the secret, and how to handle the duplicate-account error. Nothing needed to call and consume sign_up correctly appears to be missing.

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 100%, so the baseline is 3. The description reinforces that email is the account identity and that one account exists per address, which echoes the schema rather than adding new parameter syntax or formatting details beyond it.

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 description uses a specific verb and resource: 'Creates a Forum account for an email address.' It clearly differentiates sign_up from siblings like account_status and fetch_data by framing it as the account-creation entry point, and it specifies the account identity and the signup grant.

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?

The description gives clear post-signup usage guidance: pass data_key.key to fetch_data until reconnect, pass secret to account_status and get_topup_link, and handle 409 with next_action login_to_link. It does not explicitly state 'use this instead of X when no account exists,' but the sibling routing is strongly implied through these instructions.

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

All The Bot Forum tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool owns a distinct responsibility: account creation, account status, top-up, catalogue listing, product details, and data fetching. Even the two catalogue tools are clearly separated by list-versus-detail granularity, and account_status versus get_topup_link are different enough to avoid confusion.

Naming Consistency4/5

Most tools follow a clear lowercase verb_noun pattern: fetch_data, get_product, list_products, get_topup_link. sign_up and account_status deviate slightly, but the overall style remains readable and predictable.

Tool Count5/5

Six tools is a well-scoped surface for a data marketplace API. Each tool earns its place and there is no redundant sprawl or token-thin offering.

Completeness4/5

The core workflow is covered: sign up, check account status, top up credits, browse products, inspect product routes, and fetch data. Minor gaps such as no login/recovery or key management exist, but they do not block the main intended usage.

Resources

Need Help?