Loading ToolBench

Reading the current corpus…

overte-mcp MCP server · D · ToolBench

overte-mcp

Overte (open-source Vircadia-lineage metaverse) Model Context Protocol server for domain administration and in-world entity orchestration

2026-07-28+STDIO9 tools

52/100

Definition Quality61

Protocol Readiness50

Supportability38

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Overte MCP has 9 tools with reasonable naming (verb_noun pattern) and descriptions present for all. However, critical gaps undermine quality: (1) Parameter descriptions are sparse or missing for many inputs, e.g., overte_entity_spawn's 'scale' param lacks detail on behavior when omitted; (2) Output schemas are NOT documented anywhere, LLMs cannot predict return structure; (3) Error handling is absent, no guidance on recovery or retryability; (4) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (DESTRUCTIVE, WRITE, READ_ONLY); (5) Tool descriptions average ~80 chars, below the 194-char baseline for A+ tools. Naming is solid (overte_entity_spawn, overte_entity_delete, overte_nearby_entities follow verb_noun), but lack of output documentation and error guidance are major blockers for production use.

Tools (9)

overte_domain_statusread onlysource verified67/100

Retrieve connected-node telemetry and settings from an Overte Domain Server.

overte_entity_animatewritesource verified65/100

Loop-animate an entity in place (spin or bob) for a fixed duration.

overte_entity_deletedestructivesource verified58/100

Permanently delete an in-world entity.

overte_entity_spawnwritesource verified62/100

Spawn a virtual object, 3D GLB model, or Light in-world at the specified coordinates.

overte_entity_updatewritesource verified62/100

Move, resize, re-parent, or toggle an existing in-world entity.

overte_fixture_spawnwritesource verified63/100

Spawn a preset test fixture (box, cup, ball, table, chair) for gripper/manipulation testing.

overte_nearby_entitiesread onlysource verified67/100

Find real in-world entities near a point (default: the local user).

Issues (5)

CRITICALtool ↗

No output schemas documented. LLMs cannot predict return structure, field names, or types. Breaks tool chaining and forces agents to guess at response format.

overte_domain_statusoverte_entity_spawnoverte_script_injectoverte_entity_updateoverte_entity_deleteoverte_entity_animateoverte_nearby_entitiesoverte_fixture_spawnoverte_sampling_assist

HIGHtool-annotations ↗

Missing tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools marked DESTRUCTIVE (overte_entity_delete) or WRITE (overte_entity_spawn) lack formal hints. Agents cannot distinguish safe from unsafe operations.

overte_entity_spawnoverte_script_injectoverte_entity_updateoverte_entity_deleteoverte_entity_animateoverte_fixture_spawn

HIGHrecovery-guide ↗

No error handling or recovery guidance. Tools lack descriptions of failure modes, retryability, or actionable error messages. E.g., overte_entity_spawn does not document what happens if model_url is invalid.

Recommendations

Document output schemas for all 9 tools. For each, specify return type (object/array), field names, types, and whether fields are always present. E.g., overte_entity_spawn should return {entity_id: string, position: [number, number, number], created_at: string}.
Add tool annotations to fastmcp tool definitions: @mcp.tool(annotations={readOnlyHint: true}) for overte_domain_status, overte_nearby_entities; @mcp.tool(annotations={destructiveHint: true}) for overte_entity_delete; @mcp.tool(annotations={idempotentHint: false}) for write operations.
Expand parameter descriptions to 50 - 150 chars each. For overte_entity_spawn's 'scale' param, clarify: 'X, Y, Z bounding-box dimensions in meters. If null, Overte uses the model's natural dimensions (non-cubic models are stretched to fit).' For 'script_data', specify: 'JSON object passed to the script's scope. Keys become script variables.'
Add error handling guidance to tool descriptions. E.g., overte_entity_spawn: 'Returns error if model_url is unreachable or invalid GLB/FBX. Retry with a valid URL or use a built-in type (Box, Sphere) instead.'
Clarify or rename overte_sampling_assist. If it's a planning tool, rename to overte_plan_operation and document what guidance it provides. If it's deprecated, remove it or integrate its logic into other tools.

Score history

Overall score trend

First recorded score · v2 rubric

52/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	52	2026-07-28+	v2