Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

environment_configure

Save non-secret local defaults for cache size, data and cache directories, Isaac Python, and USD search URL; environment variables override stored values.

Instructions

Save non-secret local defaults; environment variables take precedence.

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

Input Schema

NameRequiredDescriptionDefault
cache_bytesNo
isaac_pythonNo
data_directoryNo
usd_search_urlNo
cache_directoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior3/5

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

With no annotations, the description still carries useful disclosure: the saved values are local and non-secret (so credentials are out of scope), they persist, and env vars override them at resolution time. It does not say where they persist, whether a call merges with or overwrites existing defaults, or what a successful call returns, which matters for a mutation tool with zero annotation coverage.

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 compact sentence with no padding, and the meaningful constraint (env vars win) is placed in a clause the reader reaches immediately. It is efficient, though its brevity edges into under-specification rather than pure conciseness.

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?

This is a five-parameter configuration mutation with no annotations, no output schema, and no per-field documentation, so the description is the only explanatory layer available—and one sentence cannot cover it. An agent would have to guess at valid values and merge/overwrite behavior before calling it safely.

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

Parameters1/5

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

Schema description coverage is 0% across five parameters, and the description names none of them—not cache_bytes, cache_directory, data_directory, usd_search_url, or isaac_python. Units, expected formats (e.g. paths vs URLs vs byte counts), and null-vs-unset behavior are all undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Save') and a resource ('non-secret local defaults'), which is better than a tautology, but 'defaults' is vague shorthand for the five configuration fields actually accepted. It never names cache, data directory, or Isaac interpreter settings, so an agent must open the schema to learn what this tool configures.

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 precedence clause ('environment variables take precedence') implies this tool is for persisting fallback values, but there is no explicit statement of when to call it, what preconditions apply, or why it differs from the sibling environment_probe. The agent is left to infer the configure-versus-inspect split on its own.

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