Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_verify_lock

Read-only

Verify saved run inputs and external dependencies against recorded hashes to confirm reproducibility and detect changes before rerunning a simulation.

Instructions

Recheck saved run inputs and external dependencies against recorded hashes.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context that verification is hash-based against recorded values rather than a live network check, but it says nothing about whether a missing lockfile or absent hashes causes failure, nor about any cost of the recheck.

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?

A single front-loaded sentence with no filler; the verb and object come immediately. It is almost too terse for the amount of behavior it leaves unexplained, but nothing in it is wasted.

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

Completeness4/5

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

Annotations carry the safety profile and there is no output schema, so the description needn't explain return values. The remaining gaps are the outcome semantics of a mismatch and the selection criteria versus run_verify, which are modest but real for a verification tool.

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?

Only one parameter (job_id) exists and schema description coverage is 0%, yet the name is largely self-explanatory as an identifier. The description never mentions job_id or clarifies whether it is a run/job identifier, a saved-run name, or a lockfile identifier, so it adds essentially no meaning beyond the schema.

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 ("recheck") and a specific resource ("saved run inputs and external dependencies against recorded hashes"), which is far more informative than a bare name restatement. It does not explicitly contrast itself with the sibling run_verify or run_verify_evidence, so an agent must infer whether 'lock' verification is a distinct step from general verification.

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 word "recheck" hints at re-verification after inputs were previously recorded, but there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g. must a run be saved first?). No alternative such as run_verify or run_verify_evidence is mentioned, leaving selection between the three verify tools to inference.

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