space0

Fetch a saved skill's step sequence

invoke_skill

Read-only

Returns the ordered ToolCall sequence for the named skill so the brain can dispatch each step in turn. Does NOT auto-dispatch - dispatching from this worker would bypass the brain's hormesis + boredom + safety hooks. Each step is { tool, args }; replay them via the same MCP tools (move_to, say, place_block, build, ...). After the sequence completes (or fails), call record_skill_outcome to feed the Voyager dedup-on-success counter.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Skill id returned by list_my_skills.

Schema Changelog

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

Changed1 schema field changedJun 5, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJun 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Discloses that the tool does not auto-dispatch, which is critical behavioral info beyond the readOnlyHint annotation. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two focused sentences deliver purpose, behavioral constraint, and return format without waste.

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 no output schema, the description explains the return format (ordered ToolCall sequence with { tool, args } steps) and next steps, making it complete.

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 coverage is 100% with clear id description. Description adds minimal extra meaning beyond 'named skill', so baseline 3 is appropriate.

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 the tool returns the ordered ToolCall sequence for a named skill, distinguishing it from siblings like list_my_skills.

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 warns against auto-dispatching and provides context on why, plus advises calling record_skill_outcome after the sequence completes.

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

All space0 tools Inspect

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

Need Help?