Skip to main content
Glama

simulation_log

Read-only

Read actual Proteus simulation log rows directly from the native item model to inspect simulation output without menu navigation, screenshots, or input emulation.

Instructions

Read actual Proteus simulation log rows directly from the native item model. No menu, screenshots or input emulation.

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

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context by saying the read happens against the native item model without menu navigation or input emulation, but it says nothing about what the log contains, whether it accumulates across runs, or how much data comes back. With annotations carrying safety, this is adequate but thin.

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?

Two tight sentences with the action front-loaded and zero padding; the negative clause about menus and screenshots earns its place by ruling out alternative retrieval paths. Slightly more expensive than needed given the parameter documentation is absent where those words could have gone.

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?

No output schema exists, so the description could reasonably say something about the shape or volume of returned rows, and it does not. Combined with a completely undocumented required 'session' parameter, an agent knows what the tool does but not how to call it correctly or what to expect back.

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?

There is one required parameter, 'session', with 0% schema description coverage, so the description must carry the burden and it does not — it never explains what a session identifier is, where it comes from, or how it scopes the log rows returned. This is the clearest gap in 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?

The description states a specific verb and resource — 'Read actual Proteus simulation log rows' — and adds the mechanism ('directly from the native item model'), which separates it from UI-driven or screenshot-based readings implied by siblings like simulation_observe. It stops short of naming any sibling explicitly, so an agent still has to infer why this beats simulation_sample or simulation_observe for a given need.

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?

'No menu, screenshots or input emulation' implies when this tool is preferred over UI-driven approaches, which is genuinely useful routing signal. However, there is no explicit statement of when to use this versus the sibling simulation_* tools, nor any prerequisite or exclusion stated outright; the guidance is implied rather than declared.

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