Skip to main content
Glama

rex_session_view

Inspect a Rex session's snapshot of windows, layouts, blocks, and focus to understand its current structure and state.

Instructions

Snapshot of a session: windows, layouts, blocks, focus (session.view).

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": "rex_session_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesSession label or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Snapshot' hints at a read, but the definition never states that it is non-mutating, what happens if the session label is unknown, whether it is expensive, or how the state is sampled at a point in time.

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

Conciseness3/5

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

It is a single short fragment with no wasted sentences, which is good, but the fragment structure and the dangling '(session.view)' reference make it read as a note-to-self rather than a front-loaded explanation. Brevity here shades into under-specification.

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?

With no annotations and no output schema, the description must carry the return contract, and it does partially by enumerating the four components of the snapshot. It stops short of describing structure, ordering, or size, so an agent knows roughly what comes back but not how to consume it.

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

Parameters3/5

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

Schema coverage is 100% for the single 'session' parameter, so the schema already explains that a label or ID is accepted. The description adds nothing about the parameter, and the parenthetical '(session.view)' is unexplained internal jargon rather than useful semantics. Baseline 3 applies when the schema does the work.

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 names the resource (a session) and the content of the result (windows, layouts, blocks, focus), which gives a reasonable idea of what is returned. However, 'Snapshot of a session' is a noun phrase rather than a clear verb+resource statement of action, and nothing distinguishes it from plausible siblings such as rex_status or rex_block_info, which could equally be read as reading session state.

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?

There is no guidance on when to call this versus alternatives, no prerequisites, and no exclusions. An agent must guess whether rex_status or rex_block_info is the better entry point for the same information.

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