Skip to main content
Glama

simulation_observe

Destructive

Samples DSIM network vectors in an owned running simulation, decodes calibrated state codes with strength awareness, and returns bounded summaries plus saved raw traces for evidence.

Instructions

Sample DSIM native network vectors with VSMDEBUG native simulation-time brackets. Strength-aware decoding only for calibrated state codes; unknowns remain unknown. Bounded polling, NOT a complete event waveform or analog/audio measurement. Saves full raw trace, returns summary/evidence. Running owned session only.

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": {
      "session": "<session>",
      "nets": "<nets>"
    },
    "name": "simulation_observe"
  }
}

Input Schema

NameRequiredDescriptionDefault
netsYes
sessionYes
wall_msNo
interval_msNo
max_samplesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses several operational behaviors: it saves a full raw trace, returns summary/evidence, only decodes calibrated state codes, and leaves unknowns unknown. It does not detail what the destructive annotation may affect, but it adds substantial context beyond readOnly=false and destructive=true.

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?

The description is compact and front-loads purpose before caveats. It is dense with domain jargon but does not waste many words; the main cost is that several terse clauses require domain knowledge to parse.

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 five-parameter, destructive, no-output-schema tool, the description covers important behavioral constraints and side effects. However, it leaves parameter-level guidance and the exact structure of the returned summary/evidence underspecified, which matters for correct invocation.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, but it only hints at 'nets' as network vectors, 'session' as an owned running session, and bounded polling for timing controls. It never explains how wall_ms, interval_ms, or max_samples should be set individually.

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 states a specific verb and resource: sample DSIM native network vectors with VSMDEBUG native simulation-time brackets. It also explicitly scopes itself away from a complete event waveform and analog/audio measurement, though the jargon keeps it from being fully self-explanatory.

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 gives clear when-not guidance by stating this is bounded polling and not a complete event waveform or analog/audio measurement. It also names a prerequisite with 'Running owned session only,' but it does not point to a specific sibling alternative when this tool is inappropriate.

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