Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_presentation_events

Read-only

Read semantic phase and spawn events from a completed simulation run's frozen spec to inspect presentation sequencing; verify physical success separately.

Instructions

Read semantic phase/spawn events from the completed run's frozen spec. No event implies physical success; inspect run_verify separately.

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": {
      "job_id": "<job_id>"
    },
    "name": "run_presentation_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuinely useful behavioral caveat that annotations cannot express: absence of an event does not imply physical success, and the 'frozen spec' phrasing signals these events are a static, immutable record rather than live state.

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 tight sentences with the substantive scope statement front-loaded and the important caveat second. Nothing is repeated from the name or annotations, and no sentence is filler.

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?

For a one-parameter read tool with no output schema, the description covers intent and the key interpretation trap, but says nothing about what the returned events look like, ordering, or what happens if the run is not yet complete. Adequate rather than 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 0%, so the description must carry the single job_id parameter, and it only partially does so by implying the id must reference a completed run with a frozen spec. It adds no format, lookup, or error detail beyond that implication.

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?

Uses a specific verb ('Read') with a named resource ('semantic phase/spawn events') and scope ('completed run's frozen spec'). It implicitly separates itself from run_verify by warning that these events are not physical-success signals, though 'semantic phase/spawn events' remains domain jargon an agent must already know.

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?

States the prerequisite implicitly (the run must be completed and have a frozen spec) and explicitly routes the agent elsewhere for physical success: 'inspect run_verify separately.' It gives no guidance versus other read-style siblings such as scene_plan_presentation or run_observe, but the primary alternative is clearly named.

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