Skip to main content
Glama
Sign In
ScreenConnect MCP Server

ScreenConnect MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

screenconnect_session_get

Read-onlyIdempotent

Retrieve a specific ScreenConnect session by its GUID to inspect session details and optionally include raw API data.

Instructions

Get one session by GUID.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYes
includeRawNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing about behavior — not what happens when the GUID is unknown, whether an error or null is returned, or anything about auth against the external system implied by openWorldHint.

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?

A single short sentence, front-loaded with no filler. It is efficient, though its brevity borders on under-specification rather than pure conciseness.

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

Completeness2/5

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

For a tool that hits an open-world external system with no output schema, the description should at least cover the undocumented includeRaw flag and what a lookup returns or does on miss. Neither is present, so an agent can call it but cannot predict its behavior.

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%. The phrase "by GUID" loosely explains sessionId, but the schema's regex pattern already imposes that format, and the second parameter includeRaw is not mentioned at all — the agent has no idea what raw data it would opt into.

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 one session by GUID" names a specific verb and resource, so the basic purpose is clear. However, it does not distinguish this tool from the sibling screenconnect_session_get_details, which also appears to fetch a single session — the agent cannot tell from the text which one to pick.

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 when-to-use or when-not-to-use guidance, no mention of alternatives like screenconnect_sessions_search or screenconnect_session_get_details, and no prerequisites stated.

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

Deploy Server

Other Tools