ScreenConnect MCP Server

screenconnect_session_get_details

Read-onlyIdempotent

Retrieve a ScreenConnect session's connections and newest-first events, preserving unknown detail fields and optionally returning the original raw payload.

Instructions

Get connections and newest-first events. Unknown detail fields are preserved in details; includeRaw returns the original payload.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "screenconnect_session_get_details"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`sessionId`	Yes
`eventTypes`	No
`includeRaw`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add behavior, and it does: it discloses the newest-first ordering of events, that unrecognized detail fields are preserved rather than dropped, and that includeRaw returns the unprocessed payload. It still omits whether limit bounds events, connections, or both, and says nothing about permissions or volume.

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, no filler, with the returned resources front-loaded and the payload-behavior caveats second. Every clause carries information.

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 output schema, the description must convey what comes back, and it partially does by naming connections, events, details, and the raw payload. However, for a tool with four parameters and zero schema descriptions, the unexplained limit and eventTypes leave real gaps an agent must guess at.

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?

Schema description coverage is 0% across four parameters, so the description must carry the load. It explains only includeRaw ("returns the original payload"); limit, its 1-500 range and default, and eventTypes are never mentioned, and the description does not state that sessionId is a GUID keying the lookup.

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?

"Get connections and newest-first events" names the resources returned but never says this operates on a specific session identified by sessionId, and it does not distinguish itself from the sibling screenconnect_session_get. The verb+resource is present but the scope and the differentiation from siblings are left implicit.

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 statement of when to use this tool rather than screenconnect_session_get or the sessions_search/list_online siblings. The only implied guidance is the word "details", which asks the agent to infer the distinction.

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

Deploy Server