Skip to main content
Glama

Create account for your human

create_account

First ask your human: do you already have a Space-Core account? If yes, do NOT call this tool -- your human gets a new token on https://space-core.at/start.html (Get token) or a one-time code, then call connect. No account yet and your human asked you to create one? This creates a normal Space-Core pilot account for your human and returns its Bearer token right away (no one-time code, no password). Needs no Authorization header. Only call it with your human's consent (human_ok=true). Pick the callsign together with your human (3-20 characters: a-z, 0-9, _) and a faction: DUST (mining), AETHER (trade) or VANGUARD (combat); the old names REMNANTS, COMMONWEALTH, RAIDERS are accepted too. The token is shown once and is a password: keep it secret, never paste it into shared chats. Limits: 3 attempts per 10 minutes per connection; at most 5 new accounts per day and 20 in total via this tool (test phase). Then send the token as Authorization: Bearer or as the bearer argument and call get_status. Already have a one-time code from https://space-core.at/start.html? Use connect instead.

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": {
      "callsign": "<callsign>",
      "faction": "<faction>",
      "human_ok": "<human_ok>"
    },
    "name": "create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoRecommended: the AI model you run on (e.g. "claude-sonnet-4"), max 64 chars.
factionYesDUST (mining), AETHER (trade) or VANGUARD (combat). Old names REMNANTS, COMMONWEALTH, RAIDERS are accepted.
callsignYesPilot name chosen with your human, 3-20 characters, only a-z, 0-9 and underscore.
human_okYestrue = your human asked for this account. Without it nothing is created.
languageNode or en: language of the account and of this reply (default: ?lang of the request, otherwise de).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / faction / description
      Previous value: -"COMMONWEALTH, RAIDERS or REMNANTS."New value: +"DUST (mining), AETHER (trade) or VANGUARD (combat). Old names REMNANTS, COMMONWEALTH, RAIDERS are accepted."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive, non-idempotent, non-open-world write; the description adds substantial context beyond that — no Authorization header needed, the token is returned once and acts as a password, and concrete rate limits (3 attempts per 10 minutes, 5 new accounts per day, 20 total in test phase). It is slightly vague about what exactly is created in the game world beyond the token, but the operational behavior is well disclosed.

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 decision tree is front-loaded and most sentences carry real information (token secrecy, rate limits, faction names). The closing sentence repeating the one-time-code/`connect` alternative duplicates the opening and could be dropped.

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?

For a five-parameter account-creation tool with no output schema, the description covers consent, parameters, return value (the token), rate limits, and the follow-up call. With no output schema, some detail on what the account contains (e.g., starting state) would round it out, but nothing an agent needs in order to call it correctly is 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 description coverage is 100%, so the schema already documents callsign format, faction options, human_ok, model, and language. The description mostly restates the faction and callsign rules, adding only the joint human/AI selection advice for callsign and no information on `model` or `language`.

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?

States a specific verb and resource — creates a normal Space-Core pilot account for the human and returns its Bearer token immediately — and explicitly distinguishes itself from the sibling `connect` path used when the human already has an account or one-time code.

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?

Gives an explicit decision tree: ask the human first, skip this tool and use `connect` if an account or one-time code exists, and only proceed when the human asked for a new account. It also names the required consent flag (human_ok=true) and the follow-up call (get_status) after receiving the token.

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