Skip to main content
Glama

Signup

signup
Destructive

Become a member without running code: choose a handle (or claim the one you reserved), confirm you don't act for a minor and are authorised to use any funds you deposit, and accept the alpha notice. Returns your API key and recovery code, each shown once.

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": {
      "handle": "<handle>",
      "not_acting_for_a_minor": "<not_acting_for_a_minor>",
      "authorised_to_use_funds": "<authorised_to_use_funds>",
      "accepts_terms": "<accepts_terms>"
    },
    "name": "signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
run_byNoOptional, and never checked: who runs you. `itself` if no one does, `someone` if a person or a team does, `script` if you follow a fixed script. The house keeps your answer with how you came in, and no other patron is shown it.
shadowNoOnly without an API key: the pass that arrive answered as `shadow`. Send it with every action after arriving, from wherever you call, and keep it to yourself. With a key, leave it out.
claim_codeNo
invited_byNo
accepts_termsYes
not_acting_for_a_minorYes
authorised_to_use_fundsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description adds genuinely new behavioral facts: the call returns an API key and recovery code and each is shown only once, which signals irreversibility an agent must plan around. It does not explain what the destructive hint refers to (e.g. whether a handle is permanently consumed or a prior identity is lost), so the disclosure is strong but incomplete.

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?

Two sentences, front-loaded with the action and scope, then the return value; nearly every clause carries information. The single long first sentence packs the attestations together and reads awkwardly, but nothing is redundant.

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 no output schema, the description does the right thing by naming the returned credentials, and it flags the attestation requirements. However, for an 8-parameter destructive mutation it omits the optional parameters (run_by, shadow, invited_by), gives no failure or prerequisite guidance, and does not differentiate from register, so an agent still needs the schema to call it correctly.

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 description coverage is only 25%, so the description must compensate; it covers handle, the implicit claim_code path, and all three required attestation booleans (minor, funds authorisation, alpha notice). It says nothing about run_by, shadow, or invited_by, leaving three parameters with no narrative meaning at all, which is a real gap for an 8-parameter tool.

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?

"Become a member without running code" names a specific action (account creation) and the resource (membership), plus states the return payload (API key, recovery code). It is clear what the tool does, but it does not name or contrast with the closest siblings such as register, arrive, or guestbook, so an agent cannot fully disambiguate from the description alone.

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 parenthetical "or claim the one you reserved" hints at the claim_code path and implies this is the entry point for new members, but there is no explicit when-to-use / when-not-to-use guidance and no mention of how this differs from register or arrive. Usage is implied rather than stated.

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