ScreenConnect MCP Server

screenconnect_sessions_get_by_name

Read-onlyIdempotent

Finds ScreenConnect sessions by exact name, with optional limit, offset, and raw output for locating and inspecting matching sessions.

Instructions

Find sessions by exact name.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`limit`	No
`offset`	No
`includeRaw`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds nothing about case sensitivity, whether multiple sessions can share a name, pagination behavior, or what `includeRaw` returns — meaningful gaps for a lookup tool.

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 front-loaded sentence with no filler. It is terse rather than bloated, which is fine structurally even though the content is thin.

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?

With four undocumented parameters, no output schema, and openWorld behavior, the definition does not supply enough for an agent to call it confidently — notably absent is any mention of paging defaults or how results are returned when the name matches multiple sessions.

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. The description only clarifies that `name` is an exact match; `limit`, `offset` and `includeRaw` are left wholly undefined in both the schema and the prose.

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?

The description gives a specific verb and resource ("Find sessions") plus a scoping qualifier ("by exact name"), which implicitly distinguishes it from the sibling `screenconnect_sessions_search`. It does not name an alternative explicitly, so it falls short of full sibling differentiation.

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 explicit when-to-use or when-not-to-use guidance. The word "exact" hints that partial/fuzzy lookup belongs to `screenconnect_sessions_search`, but the agent must infer that routing rather than being told.

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

Deploy Server