Skip to main content
Glama

screen_close

Idempotent

Close the recorded browser and let go of any app (a take still recording is thrown away).

response_detail (summary|ids|compact|full), fields (dotted paths), cursor (next page) — see the server instructions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screen_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
fieldsNo
response_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

The description does usefully disclose a real side effect — an in-progress recording is thrown away — which goes beyond the annotations. However, that disclosed data loss sits awkwardly against destructiveHint=false and idempotentHint=true, and the definition says nothing about what happens if no session exists or whether other apps' state is affected. The valuable disclosure is undercut by an undeclared behavior profile that conflicts with the annotations.

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 first sentence is front-loaded and earns its place. The second is boilerplate response-shaping text that appears copied from sibling read tools and reads oddly on a close operation, adding length without clarifying the action.

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?

Three parameters have zero schema documentation, there is no output schema, and the description never says what closing returns or how to detect that no browser was open. For a state-mutating teardown tool with a disclosed data-loss path, that leaves meaningful gaps.

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?

With 0% schema description coverage the description must carry the load, and it does partly: it names response_detail with candidate values, fields as 'dotted paths', and cursor as 'next page'. That is helpful but thin — it defers to 'see the server instructions' and never explains why a close operation would page results, leaving the cursor semantics ambiguous.

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 first sentence gives a concrete verb plus resource (close the recorded browser) and adds scope ('let go of any app'), which is more specific than the bare name. It does not name or contrast with siblings such as screen_record_stop or screen_hand_over, so an agent must infer the boundary itself.

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 statement of when to call this versus screen_record_stop or screen_hand_over; the parenthetical about a discarded take only implies 'use as last-resort cleanup'. No prerequisites (e.g. an open session) or when-not-to-use conditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.