Skip to main content
Glama

body_windows

Lists currently open window titles read-only, letting agents see what is open without screenshots or a debug port; it cannot control those windows.

Instructions

See which windows are open right now (titles only - no content, no screenshots).

This is read-only and needs no debug port, so it works even for a browser you started yourself. It CANNOT drive those windows: for that the browser needs a sanctioned connection (a debug port on a separate profile, or the extension bridge).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only behavior, explains that no debug port is required, and discloses the precondition for the write/drive capability (debug port on a separate profile or the extension bridge). What it omits is the shape of the result beyond 'titles only' — no ordering, grouping by browser, or pagination/limits.

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

Conciseness5/5

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

Three short sentences, front-loaded with the capability and its output boundary, followed by the operational caveat and the contrast case. Every sentence adds information an agent needs; nothing is redundant.

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

Completeness4/5

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

For a zero-param, read-only inspection tool with no output schema, this is nearly complete — it tells the agent what it gets back (titles) and what it cannot do. The one residual gap is whether results span all browsers or a single one, which an agent might need before calling.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly signals a no-argument call and adds no misleading parameter-shaped language.

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?

States a specific verb and resource (see which windows are open right now) and immediately bounds the scope with 'titles only - no content, no screenshots'. It implicitly distinguishes itself from tools that drive windows, though it never names a concrete sibling, so it stops just short of full differentiation.

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?

Gives clear context: use it to inspect what is open, and it works even for a browser you started yourself because no debug port is needed. It also states the exclusion — this tool cannot drive those windows, that requires a sanctioned connection — but leaves the alternative unnamed rather than pointing to a specific tool.

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