Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_plan_stream_case

Read-only

Propose a scene-derived physical evidence case using explicit per-class inner bin bounds and forbidden objects. Use it to plan simulation validation, not as acceptance or path-safety certification.

Instructions

Propose a scene-derived physical evidence case using explicit per-class inner bin bounds and forbidden objects. This is not independent acceptance or path-safety certification.

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": {
      "scene_id": "<scene_id>",
      "belt_id": "<belt_id>",
      "bins": "<bins>",
      "forbidden_objects": "<forbidden_objects>"
    },
    "name": "scene_plan_stream_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
binsYes
belt_idYes
scene_idYes
forbidden_objectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation, lowering the disclosure burden. The description adds that the output is a proposal, not acceptance or certification, which is useful behavioral context, though it does not describe the proposal's structure or any limits on the evidence it produces.

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 two tight sentences and front-loads the core action before the boundary disclaimer. There is little wasted wording, though the jargon-heavy phrasing reduces immediate clarity.

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

Completeness2/5

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

With four required parameters, a nested bins object, 0% schema description coverage, and no output schema, the definition is too thin to fully guide invocation. It identifies the tool's general purpose and boundary but omits necessary details about identifiers, bin structure, and what the proposed case contains.

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%, so the description must carry parameter meaning. It partially explains "bins" as per-class inner bin bounds and identifies "forbidden objects," but leaves scene_id, belt_id, and the nested bins structure undocumented, which is a significant gap for four required parameters.

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

Purpose3/5

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

The description names a specific verb, "Propose," and a resource, "scene-derived physical evidence case," but "case" is undefined jargon rather than a concrete artifact. The disclaimer distinguishes it from acceptance/certification, but it does not clearly differentiate it from sibling planning tools such as scene_plan_stream.

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

Usage Guidelines2/5

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

The only usage guidance is a negative boundary: "This is not independent acceptance or path-safety certification." It does not say when to choose this tool, what prerequisites are needed, or which sibling tool to use for acceptance or path-safety checks.

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