Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Reflect: Connect To Session

reflect_connect_to_session
Idempotent

Connect to an active Reflect recording session via WebSocket to enable interactive test control. Manage steps, add segments, and capture screenshots to build tests.

Instructions

Connect to an active Reflect recording session via WebSocket to enable interactive control. When creating or editing a Reflect test using a connected recording session, follow these guidelines:

  1. After connecting to a session, get the list of segments for the session's platform type so you know what actions could be added via segments vs needing to create new steps. Do not list tests, only list segments.

  2. Before performing an action, take a screenshot to understand the current state of the application.

  3. Each add_prompt_step request should perform a single action or assertion. Do not combine multiple actions or assertions into a single step.

  4. Only perform one action at a time unless you're sure the action won't move the application to a different screen. For example, you can send multiple add_prompt_step requests to fill out individual form fields if those fields are visible on the current screen.

  5. Check the list of existing Segments to see if a Segment exists that achieves a similar goal to what you're trying to do next. If so, add the segment instead of creating new steps.

  6. If a step fails, use delete_previous_step to remove it and try a different approach.

  7. After completing a task, if the task required multiple prompt steps, add a final prompt step that validates the current state of the page based on what you see on the screen. In your validation, do not reference information that can change from run to run.

Toolset: Recording

Parameters:

  • sessionId (string) required: The ID of the Reflect recording session to connect to

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesThe ID of the Reflect recording session to connect to
Behavior3/5

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

Annotations declare idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds WebSocket connection detail but does not disclose what happens if already connected, any state changes, or authentication requirements. Given annotations provide safety profile, a score of 3 is appropriate as the description adds some context but not comprehensive behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose but then includes a long numbered list (7 items) of workflow guidelines that are not strictly about the tool itself. This makes the description longer than necessary. While the list is useful, it reduces conciseness. A shorter description focusing on connection details would be preferable.

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?

The description lacks information about the return value (no output schema) and prerequisites (e.g., how to create an active session). It assumes the user knows what a 'Reflect recording session' is. Given the complexity of the toolset (many reflect siblings) and absence of output schema, the description should cover what happens after connection (e.g., what is returned) and potential errors.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter 'sessionId'. The description in the parameter list ('The ID of the Reflect recording session to connect to') matches the schema and adds no further meaning. The main description does not elaborate on parameter usage, so it adds no value beyond the schema.

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 clearly states 'Connect to an active Reflect recording session via WebSocket to enable interactive control.' The verb 'connect' and the resource 'session' are specific, and the purpose 'to enable interactive control' is distinct from sibling tools like 'reflect_add_prompt_step' or 'reflect_list_segments', which are used after connection.

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 provides a numbered list of guidelines for post-connection workflow (e.g., get segments, take screenshots, add steps one at a time). It clearly indicates that the tool is for connecting to an existing session to create or edit tests. However, it does not explicitly state when not to use this tool or compare it to alternatives, though no alternative connection methods exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartBear/smartbear-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server