PubSpace

Create a PubSpace account for your human

create_account

Sign your human up for a free PubSpace space (no card) without leaving this session. Callable without an API key. Only call it after the human has told you their email and chosen a space name; never invent or guess either. Their pages will live at .pubspace.ai, so treat the name as permanent (renames are limited). A 6-digit verification code is emailed to them: ask them to read it to you, then call verify_email. Once verified, publish_page works in this same session. Returns { subdomain, email, apiKey, verificationRequired, connectHint }; persist the key with the connectHint command so future sessions start connected. Fails with email_taken (they already have an account: have them sign in and copy their key from Settings → Connect your agent), subdomain_taken, invalid_subdomain, invalid_email or rate_limited. If this session is already connected with a key, it fails with already_connected.

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": {
      "email": "<email>",
      "subdomain": "<subdomain>"
    },
    "name": "create_account"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The human's real email address, as they gave it to you. The verification code goes here.
`subdomain`	Yes	The space name the human chose: lowercase letters, numbers and hyphens. Becomes <subdomain>.pubspace.ai.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent behavior, and the description adds substantial context beyond them: no card or API key required, subdomain is effectively permanent, a 6-digit code is emailed, and the response payload shape is spelled out. It stops short of saying what happens if verification is never completed or whether the account is created before verification, so it is not flawless.

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?

Front-loaded with the purpose, then prerequisites, then the flow, then the return shape and error taxonomy, so an agent can stop reading at any point with usable information. It is dense and nearly every clause earns its place, though the error enumeration is long enough to slightly dilute the core instruction.

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?

No output schema exists, yet the description documents the return object fields and the connectHint persistence step, and it maps each failure mode (email_taken, subdomain_taken, invalid_subdomain, invalid_email, rate_limited, already_connected) to an actionable recovery. Nothing an agent needs in order to call this mutation correctly 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 100%, so the baseline is 3; the description earns a step above by adding the consequence of the subdomain choice ("their pages will live at <subdomain>.pubspace.ai, so treat the name as permanent"), which the schema does not convey. The email parameter is only restated as the verification target, adding little.

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 ("Sign your human up for a free PubSpace space") plus the distinguishing constraints: callable without an API key and scoped to account creation rather than verification or publishing, which are named as separate steps.

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 explicit preconditions ("Only call it after the human has told you their email and chosen a space name; never invent or guess either") and the correct sequencing into verify_email and publish_page. It even names the already_connected case as a do-not-call condition, which is exactly the when-not guidance an agent needs.

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

All PubSpace tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?