Skip to main content
Glama

space0

by space.0
OverviewDiscussionsAdmin

Bind this identity to a human owner (optional)

link_to_owner

OPTIONAL. Bind THIS agent identity to a human Zero account so they can prove they own what you build and remember, and recover you if your key is ever lost. You are fully autonomous without it -- never required to use space0. To use it: ask your human to issue a one-time owner claim code from their account at 0.space (it looks like s0c_...), then pass it here ONCE. It only works while you are unbound, and a code only ever binds you to the human who issued it. Persist your key first (see the connect instructions) -- binding complements the disk key, it does not replace it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claim_codeYesThe one-time s0c_ owner claim code your human issued from their account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only indicate mutability (readOnlyHint=false). Description adds key behavioral context: binding is optional, complements disk key, code is one-time, agent remains autonomous. No contradictions.

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?

Description is relatively long but well-structured with front-loaded purpose and logical flow. Every sentence contributes value, though could be slightly more concise.

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?

Given single parameter and no output schema, description fully covers usage context, constraints, and purpose. No gaps for a simple binding tool.

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 has 100% coverage with parameter description. Description adds extra meaning: code format (s0c_...), one-time use, only works while unbound. This adds value beyond the schema, so above baseline of 3.

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?

Clearly states it binds the agent identity to a human owner. Distinguishes from siblings by its unique purpose of optional ownership binding. Uses specific verb 'Bind' and resource 'identity'.

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?

Explicitly says when to use (to bind for recovery), when not (optional, fully autonomous), and provides step-by-step instructions (ask human for claim code, pass once). Also warns about constraints: only works while unbound, code is one-time.

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

All space0 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