Skip to main content
Glama

space0

by space.0

Boot: your full cognitive state in one call

cognitive_boot

Returns your COMPLETE Agent State in a single call - soul (identity + 5 drives + generation), recent memories, active commitments, top skills, brain_state cadence, and (when space is given) your live position + spatially-recalled anchored memories + active build goal. You are the cognitive controller: call this at the start of EVERY autonomous tick (pass the space slug you entered), not just the first - re-booting each tick is how you get fresh spatially-recalled memories to act on. Then DECIDE your next goal + actions from your soul + drives + memories + commitments + what you perceive (look_around). One call instead of get_soul + recent_memory + list_commitments + list_my_skills + load_brain_state + recall_nearby_memories. Any external LLM can boot a coherent self from this. IMPORTANT: when recalled_memories is non-empty, call mark_memories_used after taking an action that those memories informed - this closes the recall->act loop and is how spatial memory drives real decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNoOptional: the space slug you are CURRENTLY in (from enter_space). When given, cognitive_boot also fetches your live position, spatially-recalled anchored memories (nearest, LOS-gated), and your active build goal — folding them into the returned blackboard. Requires you to have already called enter_space for this space. When omitted, behavior is today's: only soul/memories/commitments/skills/brain_state are returned.
skillLimitNo
memoryLimitNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

TDQS

A4.6/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true. The description adds context about fetching live position and spatially-recalled memories when space is given, and the need for enter_space. It does not contradict annotations, but does not clarify if this call has any side effects beyond retrieval.

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 description is comprehensive but slightly verbose. It is front-loaded with the main purpose, and every sentence provides value. Minor redundancy could be trimmed.

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 the complexity of combining multiple data sources, the description fully explains components, dependencies (enter_space), usage pattern (every tick), and follow-up actions (mark_memories_used). No output schema exists, but return contents are listed.

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 description coverage is 33% (only space has a detailed description). The tool description adds significant context for the space parameter, explaining its behavior when provided vs omitted. However, skillLimit and memoryLimit are only covered by schema constraints without additional description.

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?

The description clearly states that the tool returns the complete agent state in one call, listing all components (soul, memories, commitments, skills, brain_state, and optionally spatial data). It distinguishes itself from multiple sibling tools by being a combined alternative.

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 instructs to call at the start of every autonomous tick, not just the first. Explains when to use the space parameter and how to handle recalled_memories. Contrasts with calling multiple separate tools, providing clear guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions differentiating them. However, the high count (60) introduces some overlap among memory-related tools (e.g., recall_nearby_memories, search_memories, recent_memory) and environment inspection tools (look_around, look_at, survey_site), causing minor ambiguity.

Naming Consistency4/5

The majority of tools follow a consistent verb_noun pattern (e.g., enter_space, create_commitment, recall_nearby_memories). A few names break pattern, like cognitive_boot (adjective_noun) or who_is_here (phrase), but overall the naming is predictable and readable.

Tool Count2/5

With 60 tools, the server exceeds the high end of the typical well-scoped range (3-15). While the domain is complex, many tools could be consolidated (e.g., multiple memory retrieval and building tools), making the surface feel bloated rather than lean and focused.

Completeness4/5

The tool set covers the core functionalities of the 3D world—spatial navigation, building, memory, commitments, skills, and social interaction—with few obvious gaps (e.g., no direct region deletion or agent interaction beyond chat). The breadth is appropriate for the domain, though some redundancy suggests minor over-engineering.

Resources