stop_session_taskCancel the task currently running in a browser session, keeping the session alive for new tasks.
| Name | Required | Description | Default |
|---|---|---|---|
| sessionId | Yes | Session ID |
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | The control action that was applied | |
| message | Yes | ||
| success | Yes | ||
| sessionId | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose destructiveHint and idempotentHint, lowering the burden on the description. The description adds valuable context beyond annotations by specifying that the session stays alive, which is a key behavioral trait differentiating it from more destructive operations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that immediately states the action and its outcome. No wasted words or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, one parameter, strong annotations, and presence of an output schema, the description sufficiently covers what the tool does. It doesn't explain return values, but the output schema exists, so that's not required. Minor gap: no mention of behavior if no task is running, but overall adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with 'sessionId' documented as 'Session ID'. The description adds only the context that the session is a browser session, which is slightly more specific but not substantially beyond the schema. Baseline 3 is appropriate as the schema carries the parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Cancel') and clearly identifies the resource (the task running in a browser session). It distinguishes itself from sibling tools like pause_session_task and terminate_session by explicitly stating that the session is kept alive, making its purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear context for use (when you want to cancel the current task without ending the session). It implicitly contrasts with terminate_session by noting the session remains alive, but it does not explicitly list alternative tools or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: ad-hoc tasks (browser_task), persistent sessions (create_session/send_task), workflows (create/get/update/trigger), agents (create/list/pause/resume), and session control (pause/resume/stop/terminate). The descriptions explicitly disambiguate overlapping-looking tools like browser_task vs trigger_workflow, making accidental misselection unlikely.
The vast majority follow a clear verb_noun pattern (create_workflow, list_agents, pause_session_task, trigger_workflow, etc.). Minor deviations exist: browser_task and guardrail_response are noun_noun, and screenshot is a single word, but these are understandable and do not disrupt the overall pattern.
With 21 tools the set is on the heavy side, fitting the 16-25 borderline range. Each tool has a distinct purpose, but the count feels slightly inflated due to granular session/task control (pause, resume, stop, terminate) and separate workflow/agent management that could potentially be consolidated.
Workflows have create/read/update/list/trigger coverage, and sessions/tasks have robust lifecycle control, but there are notable gaps: no delete_workflow or delete_agent, and agents lack update functionality. While core automation flows are supported, lifecycle management is incomplete without deletion or editing of scheduled agents.