Skip to main content
Glama

Create a catchy-me account

sign_up

Registers a new catchy-me account and emails a 6-digit code to confirm it (then confirm_sign_up). Set accept_terms=true ONLY after the user has read and agreed to the Terms of Use and the Privacy Policy (their links: catchy_info terms_of_use / privacy_policy) — ask them first. Without a password one is generated and returned once: give it to the user. Returns signup_token for confirm_sign_up. [REST: POST /api/auth/register/start]

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": {
      "name": "<name>",
      "email": "<email>",
      "accept_terms": "<accept_terms>"
    },
    "name": "sign_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoThe account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
nameYes
emailYes
inviteNoAn invite code, when registration is by invitation.
passwordNo
accept_termsYesThe user agreed to the Terms of Use and the Privacy Policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"The account's language (messages, the texts of its searches). Default en."New value: +"The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en."
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "ru",
      -  "en"
      -]New value: +[
      +  "ru",
      +  "en",
      +  "es",
      +  "de",
      +  "fr",
      +  "pt",
      +  "ja"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the concrete side effects: a 6-digit code is emailed, a password is generated and returned exactly once and must be given to the user, and a signup_token is returned for confirm_sign_up. These are non-obvious, non-recoverable behaviors that the structured fields do not convey, and they are consistent with the annotations.

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 definition is dense and front-loaded: primary action first, then the follow-up tool, then the consent rule, then return values. Every clause carries operational meaning, though the embedded REST endpoint note and the compressed parenthetical about legal links slightly clutter the middle.

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?

For a 6-parameter, non-idempotent registration mutation with no output schema, the description covers what is created, what is emailed, what is returned (one-time password, signup_token), what to do next, and how to handle legal consent. Nothing an agent needs in order to call it correctly and follow up is missing.

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 only 50%, so the description must carry weight, and it does for the two most ambiguous parameters: accept_terms (must be true only after explicit user consent, ask first) and password (omit and a one-time generated one is returned). The invite parameter remains undocumented in both places, and name/email/lang get no added context, keeping this below a 5.

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 precise verb+resource ("Registers a new catchy-me account") and immediately distinguishes the flow from its sibling by naming confirm_sign_up as the follow-up step. An agent knows exactly what this tool does and what must happen next without opening the schema.

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 explicit preconditions for accept_terms (only after the user has read and agreed to the Terms and Privacy Policy), tells the agent to ask the user first, and points to catchy_info for the legal links — strong when-to-use guidance for the trickiest field. It does not state the when-not case, e.g. that an existing account should use sign_in instead, so it falls short of full alternative coverage.

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.

Resources