Skip to main content
Glama
Sign In

Spacery

by io.github.lukehollis
OverviewDiscussionsAdmin

Create space

create_space

Creates a space for one capture. An account that does not pay for hosting yet gets its first space as a free private preview: upload and process it with no payment. After that, it returns a Stripe Checkout link for the plan the person chose (pay as you go when none is given) for them to pay; then call wait_for_payment. Never ask for card details.

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": {
      "title": "<title>"
    },
    "name": "create_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoOptional plan name or ID from list_plans.
titleYesTitle of the space, 1 to 200 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare it is a non-idempotent write; the description goes well beyond that by disclosing the free-preview path, that the response contains a Stripe Checkout link, which plan is chosen by default, and the follow-up call wait_for_payment. These are behavioral facts an agent could not infer from structured fields.

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?

Four short, front-loaded sentences that each carry information: creation, free-preview condition, payment link plus follow-up call, and the card-details prohibition. Slightly dense but no filler.

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?

No output schema exists, and the description compensates by describing what is returned (a Stripe Checkout link) and the required follow-up tool. It stops short of describing the created space itself (e.g., its ID or status), which an agent likely needs to chain into later calls.

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, but the description adds real semantic value beyond the schema by explaining the default behavior when 'plan' is omitted (pay as you go when none is given). It does not add anything for 'title', which the schema already covers.

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?

Opens with a specific verb+resource and a scope qualifier ('Creates a space for one capture'), so the agent knows exactly what object is produced. It does not explicitly contrast itself with create_tour or draft_tour, but the capture-scoped framing is enough to keep it distinct.

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 concrete when-to-use context (first space is a free private preview for non-paying accounts), names the alternatives and their conditions (plan from list_plans, default to pay-as-you-go when none is given), and states the required next step: call wait_for_payment. It also gives an explicit prohibition ('Never ask for card details').

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

All Spacery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources