Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

environment_probe

Read-only

Inspect configured runtime and GPU settings before starting Isaac Sim, so you can verify the environment and avoid failed launches.

Instructions

Inspect configured runtime and GPU without starting Isaac Sim.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "environment_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuine behavioral trait beyond that: the probe does not launch Isaac Sim, telling the agent it is cheap and side-effect-free at the process level. It stops short of describing what environment facts are actually gathered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and resource, with the 'without starting Isaac Sim' qualifier placed where it matters most. No filler or redundancy.

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?

For a zero-parameter read-only probe this is nearly complete, and the no-Isaac-Sim guarantee is the key operational fact. Since there is no output schema, a brief note on what the probe reports (runtime versions, GPU model, driver) would have closed the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly implies no configuration input is required.

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 gives a specific verb (Inspect) and resource (configured runtime and GPU), which is far more informative than the bare tool name. It implicitly separates itself from environment_configure by emphasizing inspection of already-configured state, though it never names that sibling explicitly.

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?

The phrase 'without starting Isaac Sim' implies a lightweight pre-flight check rather than a full run, which hints at when to reach for it. There is no explicit statement of when to prefer this over environment_configure or what preconditions must hold, so guidance remains inferred.

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