Skip to main content
Glama

screen_status

Read-only

Can you record a demo on the user's computer right now? Call first. Says whether the Arsaze desktop app is connected, its platform, and whether it can drive the user's own apps (Windows, macOS) or only web pages. How it works: screen_open a page (or screen_list_apps + screen_open_app), screen_look / screen_act to rehearse, screen_record_start, perform the flow narrating each step with action 'say', screen_record_stop: Arsaze cuts the take (zooms, captions, dead time removed) and puts it on a new project's timeline. The user approves in Arsaze before anything is opened.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
fieldsNo
response_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds genuine context beyond that: what signals the response carries (connected state, platform, native-vs-web capability) and the important constraint that the user approves in Arsaze before anything is opened. It says nothing about latency, auth, or what a disconnected result looks like, so it stops short of full disclosure.

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

Conciseness2/5

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

Structure is inverted: a rhetorical question leads, then a long workflow narrative that mostly documents sibling tools (screen_open, screen_act, screen_record_start) rather than this one, and only at the end do the parameters appear. Substantial text is spent on the recording pipeline — zooms, captions, dead-time removal — which belongs to screen_record_stop's definition.

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

Completeness3/5

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

There is no output schema, so the description must convey return values; it does name the three signals the caller gets back, which is adequate. However, it omits what the agent should do on each outcome (e.g., connected vs. not, native vs. web-only) and offloads parameter detail to server instructions, leaving the decision logic after the call underspecified.

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 0% across three optional parameters, so the description must compensate, and it partly does: it supplies the response_detail value set (summary|ids|compact|full), explains fields as dotted paths, and identifies cursor as next-page pagination. It then defers to "see the server instructions," leaving the actual path syntax and detail-level tradeoffs unexplained, and the listed enum values are not enforced in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The actual purpose is stated clearly in the second sentence: reports whether the Arsaze desktop app is connected, its platform, and whether it can drive native apps (Windows, macOS) or only web pages. But it is buried behind an opening rhetorical question ("Can you record a demo on the user's computer right now?") that reads like a task request rather than a description of a status check, so the agent must read past a misleading lead-in to find the verb+resource.

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?

"Call first" explicitly establishes this as the prerequisite step, and the description names the downstream sequence and the alternatives within it (screen_open vs. screen_list_apps + screen_open_app, screen_look/screen_act, screen_record_start/stop). It never states when not to call it or what to do if the app is disconnected, but the ordering guidance is unusually concrete.

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.