Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_verify_evidence

Read-only

Rechecks saved output hashes for a job to confirm evidence integrity; does not verify signatures or task success.

Instructions

Recheck saved output hashes; this is not a signature or task-success check.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 structurally. The description adds a genuinely useful scope limit by excluding signature and task-success semantics, preventing misuse. However, it says nothing about behavior on hash mismatch, missing hashes, or what a failed recheck yields, which are the things an agent would actually need to know.

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?

One compact sentence with the core action front-loaded and no filler. It is arguably too terse rather than bloated, but nothing in it needs removing.

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?

For a read-only verification tool with a mandatory identifier and no output schema, the description should explain the job_id's provenance and roughly what a pass/fail recheck reports. Neither is present, leaving the agent able to understand the concept but not to call it confidently.

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?

The single required parameter job_id has 0% schema description coverage and the description does not mention it at all. There is no indication of what a job_id refers to, where it comes from, or what happens if an invalid or completed job is supplied. This is the main weakness of the definition.

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+resource: 'Recheck saved output hashes'. It also draws a boundary against two adjacent concepts (signature checks, task-success checks), which helps separate it from the run_verify* siblings. It stops short of naming which stored job artifact the hashes belong to, so it is clear but not fully self-contained.

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

Usage Guidelines3/5

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

Usage is only implied by the negative framing: it tells the agent what this is NOT, but never states when to prefer it over run_verify, run_verify_lock, or run_verify_passive_suite. An agent can infer 'use this to re-validate already-saved output integrity', but that inference is not spelled out.

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