Skip to main content
Glama

screen_result

Read-only

The result of a screen_* call that came back still running (waiting for the user to allow it, or screen_record_stop still cutting and rendering): pass its command_id. Returns what that call would have.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command_id": "<command_id>"
    },
    "name": "screen_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
fieldsNo
command_idYes
response_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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. The description usefully explains why the tool is non-idempotent by describing the pending states (awaiting user approval, still rendering). It does not say what actually happens on a call made before the work finishes — whether it returns another pending marker, blocks, or errors — which is the key behavior an agent needs.

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?

Purpose and trigger are front-loaded, which is good, but the first sentence is a long parenthetical fragment and the second trails off into a dash list that defers to 'the server instructions.' It is short with no filler, yet the structure is choppier than it needs to be.

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 is the only place a caller learns what comes back, and 'returns what that call would have' plus the response_detail/fields/cursor hints covers that at a basic level. What is missing is the pending-case semantics (retry cadence, whether to poll again) and any pointer more concrete than 'see the server instructions.'

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?

Schema description coverage is 0%, so the description has to carry the parameters, and it names all four with added meaning: command_id identifies the pending call, response_detail enumerates summary|ids|compact|full (values absent from the schema), fields takes dotted paths, and cursor is a next-page token. Only the command_id format and per-option tradeoffs remain unexplained, which is a modest gap against a total schema-coverage void.

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 description gives a specific verb and resource: it fetches the eventual result of an asynchronous screen_* call by command_id, and says it 'returns what that call would have.' That makes the purpose concrete and distinct from the act/record siblings. It does not, however, distinguish it from screen_status, which an agent could reasonably think is the polling counterpart.

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?

It states the trigger condition precisely: use this when a screen_* call came back 'still running' because the user hasn't allowed it yet or screen_record_stop is still cutting/rendering. That is a clear when-to-use. The gap is the absence of any exclusion or routing guidance relative to screen_status, so the agent must guess which one is the polling entry point.

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.