Skip to main content
Glama

ocr_frames

Extract on-screen text such as slides, code, UI, or subtitles from video frames; returns timestamped recognized text without images. Runs locally to save tokens and avoid cloud processing.

Instructions

Read the TEXT shown in a video (slides, code, UI, burned-in subtitles) without returning images, so it is cheap in tokens. Frames come from scene changes (default) or even spacing. Output: timestamp and recognised text per frame. Runs locally (rapidocr), no cloud.

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": {
      "url": "<url>"
    },
    "name": "ocr_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
urlYes
modeNoscenes
startNo
n_framesNo
max_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 discloses the token-cost profile (no images returned, cheap), processing location (local rapidocr, no cloud), frame-selection behavior, and the output shape (timestamp plus text per frame). It omits error/edge behavior for unreadable or text-free videos, but the core behavioral profile is covered.

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 tight sentences with zero waste. The capability statement is front-loaded, followed by frame-selection behavior and output/cost details in a logical order.

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?

An output schema exists, so the return-value summary is a bonus rather than a necessity. However, for a six-parameter tool with no annotations and no schema descriptions, the definition leaves too many arguments uninterpreted to be fully self-sufficient.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, and the description only clarifies one of them: the mode choice between scene changes (default) and even spacing. The url, start, end, n_frames, and max_chars parameters receive no explanation, including non-obvious behaviors like time-range clipping and character truncation.

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: read the TEXT shown in a video, with concrete examples (slides, code, UI, burned-in subtitles) and an explicit scope limit (no images returned). It implicitly separates itself from audio transcription, but no sibling tool is named, so the differentiation is inferential rather than explicit.

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?

Usage is implied by the framing ('read text shown in a video') rather than stated as a when-to-use rule. There is no explicit guidance on when to prefer this over transcribe_video or watch_video, and no stated prerequisites or exclusions.

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