Skip to main content
Glama

rex_list

Lists sessions, windows, blocks, or clients on a Rex server; include a session label or ID to list windows or blocks.

Instructions

List sessions, windows, blocks, or clients. session is required for windows and blocks.

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": {
      "kind": "<kind>"
    },
    "name": "rex_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
sessionNoSession label or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. "List" implies a safe read, but nothing states whether results are paginated, how large they can be, whether sessions/clients accept a session filter, or what happens when a bad session label is passed. For a tool with zero annotation coverage this leaves meaningful gaps.

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?

Two short sentences, zero filler, with the enumeration front-loaded and the conditional requirement immediately after. Nothing needs trimming and nothing is buried.

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 2-parameter read tool with no output schema, the definition covers invocation correctly, but it never hints at the shape of results across four different kinds or at volume/pagination limits. Adequate to call, thin on what to expect back.

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?

Schema coverage is only 50% (only `session` is documented, as "Session label or ID"), but the description compensates by disclosing a real conditional constraint not present in the schema: `session` is required for windows and blocks. That materially changes how the agent calls the tool.

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?

States a specific verb ("List") plus the four resource types it enumerates (sessions, windows, blocks, clients), which lets an agent distinguish it from siblings like rex_actions_list, rex_api_list, or rex_status. It stops short of explicitly saying how it differs from those siblings.

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 conditional clause "`session` is required for windows and blocks" gives real when-to-use guidance for the parameter. However, it offers no guidance on when to pick this over rex_status, rex_session_view, or rex_events_poll, so the agent must infer selection from resource names alone.

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