Skip to main content
Glama

simulation_inputs

Read-only

Reads calibrated BUTTON and LOGICSTATE inputs in a running ISIS simulation started via simulation_control, using a session token to query circuit input states without desktop access.

Instructions

Read calibrated BUTTON/LOGICSTATE inputs in an owned RUNNING ISIS simulation. Returns epoch/context/EID-bound token. Start with simulation_control; restart invalidates old tokens. No desktop input.

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>"
    },
    "name": "simulation_inputs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

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?

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, yet the description still adds real behavior: the call requires an owned running simulation, returns an epoch/context/EID-bound token, and that token is invalidated by a restart. It omits error behavior (e.g. what fails when the simulation is not running) but the token lifecycle disclosure is substantive.

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?

Four short sentences, each carrying distinct information, with the core action and the prerequisite front-loaded. The telegraphic phrasing ('No desktop input') is slightly cryptic but adds a useful negative constraint rather than waste.

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 one-parameter, no-output-schema tool the description covers return semantics, prerequisites and invalidation reasonably well. It leaves unclear what 'epoch/context/EID-bound' means concretely and which tools consume the token, and it says nothing about the one input parameter.

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 schema has one parameter, 'session', with 0% description coverage, and the description never mentions it or explains what a session identifier means or where to get it. With coverage this low the description is supposed to compensate, and here it does not.

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?

Uses a specific verb ('Read') with a narrowly scoped resource ('calibrated BUTTON/LOGICSTATE inputs') and a precondition ('owned RUNNING ISIS simulation'). This is far more specific than siblings like simulation_observe or simulation_sample, though it does not explicitly contrast itself with them.

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?

'Start with simulation_control' gives an explicit ordering prerequisite, and 'restart invalidates old tokens' gives a clear condition for re-obtaining state. It stops short of naming which sibling to use when input reading is not the goal, so it is clear context rather than full when/when-not guidance.

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