mcp-daktela

Overview Schema Source Related Servers Discussions Admin

list_realtime_sessions

Get current agent sessions in real time, showing online status, state (Idle/Paused/Session), extension, and pause reason.

Instructions

List currently active agent sessions (real-time snapshot). Shows which agents are online, their state (Idle/Paused/Session), extension, and pause reason.

Args: skip: Pagination offset (default: 0). take: Number of records to return (default: 200).

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

Input Schema

Name	Required	Description	Default
`skip`	No
`take`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool is a real-time snapshot (non-persistent) and enumerates the session state fields. However, it does not explicitly state that it is read-only, mention pagination limits or ordering, or address potential changes between calls, leaving some ambiguity.

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?

The description is concise, front-loaded with the purpose, and includes a clearly formatted Args block with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with an output schema available, the description sufficiently covers purpose, returned fields, and parameter semantics. It does not need to explain return values since the output schema exists, and the tool's low complexity means no additional prerequisites or side effects need to be detailed.

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 0%, but the description includes an Args section that explains skip as pagination offset and take as number of records, adding meaning beyond the raw schema. The explanations are clear but simple, without additional constraints or examples.

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

Purpose5/5

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

The description uses a specific verb 'List' with a resource 'realtime sessions' and explains that it provides a real-time snapshot of currently active agent sessions. It also lists the displayed fields (state, extension, pause reason), which differentiates it from sibling tools like list_pauses or list_users.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies usage for getting a current snapshot of active sessions (real-time), distinguishing it from historical list tools. However, it does not explicitly mention alternatives or exclusions, which prevents a 5.

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