Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_verify_passive_suite

Read-only

Validates a passive-network positive with required isolated controls; checks case bytes, source changes, physical clocks, runtime settings, and evidence locks. Missing controls reject P2/P3 stages.

Instructions

Read-only acceptance of a frozen passive-network positive plus its required isolated controls. control_job_ids maps no_trigger, broken_rope and/or locked_door to completed distinct job IDs. Case bytes, source changes, sampled physical clocks, runtime settings and evidence locks are checked; missing controls cannot accept a P2/P3 stage. This checks physical acceptance, not final video or artistic quality.

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": {
      "positive_job_id": "<positive_job_id>",
      "control_job_ids": "<control_job_ids>"
    },
    "name": "run_verify_passive_suite"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_pathNo
control_job_idsYes
positive_job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavior beyond the readOnlyHint: it discloses the validation set that is checked, the requirement that control job IDs be completed and distinct, and the consequence that missing controls cannot accept a P2/P3 stage. It remains silent on the cost/time of the run and on the shape of the acceptance result, which keeps it from a 5.

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?

Three sentences, front-loaded with the core action, then constraints, then scope limit. Every sentence carries information, though the density of domain jargon (P2/P3, physical clocks, evidence locks) makes it slower to parse than necessary.

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 verification gate with a nested object parameter and no output schema, the description covers the inputs and the acceptance condition but says nothing about what a result contains or how a failure is reported. The undocumented optional case_path leaves an agent unsure when to supply it.

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 has to carry parameter meaning. It does this well for control_job_ids by naming the expected keys (no_trigger, broken_rope, locked_door) and the constraint that values are completed distinct job IDs, but positive_job_id is only implied by 'positive' and the optional case_path is never mentioned at all.

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?

States a specific verb and resource: 'read-only acceptance of a frozen passive-network positive plus its required isolated controls', then enumerates the checks (case bytes, source changes, physical clocks, runtime settings, evidence locks). It is distinguishable from run_verify_evidence and run_verify_lock by mentioning evidence locks and case bytes as items checked, but it never explicitly contrasts itself with those siblings, so differentiation is inferential rather than stated.

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?

Gives a clear use condition (accepting a P2/P3 stage) and an explicit exclusion ('This checks physical acceptance, not final video or artistic quality'), plus the prerequisite that controls must be completed distinct job IDs. It stops short of naming an alternative tool for the cases it excludes, so there is no when-not routing.

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