Skip to main content
Glama
Sign In
FreezeText MCP

FreezeText MCP

by juergenkoller-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

capture_screen

Freeze the current screen and extract all visible text using OCR. Recognize text from videos, popups, or protected PDFs instantly.

Instructions

Freezes the screen and recognizes text via OCR (Apple Vision). Returns the recognized text from the current screen.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses 'freezes the screen' and uses Apple Vision, but lacks details on permissions, potential UI disruption, error handling, or behavior when no text is detected.

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?

Two concise sentences: first states action, second states return value. No redundancy or extraneous information.

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?

The description covers the basic purpose and return, but given no output schema, it should clarify return format (e.g., string, empty string if no text). The phrase 'freezes the screen' could be elaborated to indicate it's a single capture. Adequate but not exhaustive.

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?

There are zero parameters, so schema coverage is 100% by default. The description adds no parameter info, but none is needed. Baseline of 4 applies.

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

Purpose5/5

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

The description clearly states the tool's action: 'Freezes the screen and recognizes text via OCR (Apple Vision).' It specifies the resource (the active screen) and the output (recognized text). This distinguishes it from siblings like 'capture_region' (region-specific) and 'ocr_image' (image file OCR).

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?

No guidance on when to use this tool versus alternatives (e.g., 'capture_region' for partial screen, 'ocr_image' for existing images). No mention of prerequisites or exclusions.

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

Deploy Server

Other Tools