Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_verify

Read-only

Verify completed simulation evidence against an independent pinned local case, checking contact, suction, moving, repeated, domino, parallel, stream, mechanism, and passive-network schemas.

Instructions

Check completed physical evidence against an independent pinned local case. Types: contact, suction, moving, repeated, domino, parallel, stream, mechanism, passive_network. Passive schemas infer their type. Mechanism detached_drawer and network no_trigger/broken_rope/locked_door modes require the matching reference_job_id and isolated declared changes. A single positive network run does not accept the whole stage: use run_verify_passive_suite with its frozen required controls. This verifier only reads measurements and never releases or moves a mechanism.

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_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNopositive
job_idYes
case_pathNo
case_typeNo
reference_job_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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, yet the description adds domain-specific confirmation that it 'only reads measurements and never releases or moves a mechanism' plus the prerequisite that changes must be isolated and a matching reference job supplied for certain modes. That is meaningful behavioral context beyond the annotations; it stops short of describing result outcomes or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core scope and the alternative-tool warning are front-loaded, but the middle sentences are dense and jargon-packed ('isolated declared changes', 'frozen required controls'), reading as a run-on paragraph rather than structured guidance. No sentence is clearly wasted, but comprehension cost is high.

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?

With no output schema and a read-only tool, the description covers prerequisites and the sibling handoff reasonably well. However, for a 5-parameter verifier with zero schema coverage it leaves the parameter relationships (case_path vs reference_job_id, mode semantics) under-specified.

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 0%, so the description carries the load and partially does: it explains that the type list corresponds to case_type, that passive schemas infer their type, and that reference_job_id is mandatory for certain modes. It never clarifies the distinction between case_path and reference_job_id, what mode values other than 'positive' mean, or which job_id is being verified.

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 gives a concrete verb+resource: 'Check completed physical evidence against an independent pinned local case,' and names the sibling it is not (run_verify_passive_suite). The enumerated case types add scope, though the domain jargon ('pinned local case', 'declared changes') keeps it from being instantly parseable.

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?

It supplies real routing guidance: mechanism detached_drawer and network no_trigger/broken_rope/locked_door modes require reference_job_id, and whole-stage acceptance must go to run_verify_passive_suite with its frozen controls. It does not distinguish itself from run_verify_evidence or run_verify_lock, but the critical when-not condition is explicit.

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