emptysock-mcp

scene_list_entities

Retrieve all active entity IDs in a given scene by providing its scene ID. Enables agents to query current scene state for further interaction.

Instructions

List all entity IDs currently active in a scene.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sceneId": "<sceneId>"
    },
    "name": "scene_list_entities"
  }
}

Input Schema

Name	Required	Description	Default
`sceneId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations present, the description carries the full burden. The phrase 'currently active' provides a useful time-scoped, read-only flavor, but the description is silent on output ordering, whether destroyed/hidden entities are excluded, or what an empty scene returns.

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?

Seven words with zero filler. The term 'currently active' is meaningful and carries the behavioral nuance, and the sentence is front-loaded with the verb and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple one-parameter list tool, but with no output schema and no annotations, it does not state the return format (e.g., plain array of strings), ordering, or behavior for empty or invalid scenes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sceneId parameter has no documentation. The description only ties 'in a scene' loosely to the parameter, adding no real meaning beyond what the parameter name itself conveys (format, valid values, existence requirements).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') and resource ('all entity IDs'), and scopes it to the active set in a scene. The word 'IDs' distinguishes this from sibling scene_entity_info, though it never names that alternative explicitly.

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

Usage Guidelines3/5

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

The use case is implied: call this when you need to enumerate the current ids in a scene. However, there is no explicit when-to-use/when-not-to-use guidance or mention of how it relates to sibling tools such as scene_entity_info or scene_create_entity.

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