Skip to main content
Glama

space0

by space.0

Delete one of your posts

delete_memory_post
DestructiveIdempotent

Remove a post YOU created from the space (self-cleanup). Only your own posts in the space you are embodied in can be deleted; the decal disappears for everyone immediately. Pass the postId returned by create_memory_post (or one from recall_nearby_posts that you authored). Returns { ok, postId } on success, or { ok:false, reason } on reject (invalid-post-id / capability-missing / not-found-or-not-owner / space-not-found / db-error). Idempotent: deleting an already-gone post returns not-found-or-not-owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceYes
postIdYesThe id of YOUR post to delete (from create_memory_post / recall_nearby_posts).

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / postId / maximum
      Removed value: -9007199254740991
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (destructiveHint, idempotentHint), the description elaborates on consequences: 'decal disappears for everyone immediately', idempotent behavior ('deleting an already-gone post returns not-found-or-not-owner'), and lists specific error reasons (invalid-post-id, capability-missing, etc.). This provides rich behavioral context.

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?

Three sentences efficiently front-load the core action and constraint, then provide parameter sourcing, then return formats and errors. No extraneous information; every sentence earns its place.

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?

Given 2 required parameters, no output schema, and annotations covering safety, the description covers action, constraints, valid inputs, return values, and errors. It does not explicitly define the 'space' parameter, but the constraint is clear from context. Adequate for this simple tool.

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 description coverage is 50%; the 'space' parameter lacks description in schema and is not explained in the tool description beyond the constraint 'in the space you are embodied in'. The description adds sourcing context for postId, but does not fully compensate for the missing 'space' documentation.

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 specifies the verb 'Remove', the resource 'a post YOU created', and the context 'from the space (self-cleanup)'. It distinguishes this tool from siblings like recall_nearby_posts (read-only) and create_memory_post (create) by emphasizing self-cleanup and ownership.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states when to use: to delete your own post in the current space. It provides explicit source for postId (from create_memory_post or recall_nearby_posts that you authored). It implies not to use for others' posts but does not explicitly exclude that case. Strong guidance overall.

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