Skip to main content
Glama
Sign In
FreezeText MCP

FreezeText MCP

by juergenkoller-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

capture_region

Capture a specific screen region and extract its text using OCR by specifying coordinates.

Instructions

Captures a specific screen region and recognizes its text via OCR. Coordinates in screen points.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "capture_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate of the region's top-left corner
yYesY coordinate of the region's top-left corner
widthYesWidth of the region
heightYesHeight of the region

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It implies a read operation but does not confirm non-destructive behavior, side effects, or what 'captures' entails (e.g., screenshot vs. selection).

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 sentences, front-loaded with action and result, no wasted words.

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?

With no output schema and 4 required params, the description should hint at return value or effect, but omits any such information, leaving agents uncertain about what the tool returns.

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 input schema has 100% parameter descriptions, and the description adds 'Coordinates in screen points,' clarifying the unit beyond the schema's coordinate labels.

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 captures a screen region and performs OCR, distinguishing it from siblings like capture_screen (full screen) and ocr_image (OCR on existing image).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a hint about coordinate units but does not explicitly state when to use this tool versus alternatives (e.g., capture_screen for full screen, ocr_image for separate OCR).

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