Skip to main content
Glama
Sign In
Foldline

Foldline

by alireza12t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Check on-screen text timing

check_reading
Read-only

Checks that on-screen text stays fully in frame long enough to read, returning only failures and a count.

Instructions

Checks that every on-screen text stays fully in frame long enough to read (the page must expose window.TEXTS(t)). Returns only the failures and a count.

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": {
      "demo": "<demo>"
    },
    "name": "check_reading"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoQuery string passed to the page as location.search, e.g. 'lang=en&cut=b'.
demoYesFolder that holds the film's index.html (absolute path, or relative to the library root).
sizeNoFrame size WxH, even numbers. Default 1920x1080; 1080x1920 for a vertical Short.
stepNoSeconds between checks. Default 0.04.
cjk_cpsNoCJK characters per second. Default 4.5.
latin_cpsNoLatin characters per second. Default 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds genuine behavior beyond that: the tool drives a page that must expose window.TEXTS(t), and it returns only failures plus a count rather than a full report. It does not mention browser/headless requirements or runtime cost, but the precondition and return shape are substantive additions.

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, no filler, with the functional claim front-loaded and the hard precondition and return behavior following immediately. Every clause carries information an agent needs.

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

Completeness4/5

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

For a six-parameter read-only checker with full schema coverage, the definition covers purpose, precondition, and return shape. Remaining gaps are minor, such as what a failure entry looks like and the cost of loading a page per check.

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 100%, so every parameter (q, demo, size, step, cjk_cps, latin_cps) is already documented with defaults and constraints. The description adds no additional parameter meaning, so the baseline 3 applies.

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 (checks) and a specific property of the artifact (on-screen text stays in frame long enough to read), which clearly separates it from audio-oriented siblings like check_voice and make_voice. It does not explicitly name an alternative, but the resource is precise enough to route correctly.

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 rather than spelled out: use it on a film page that exposes window.TEXTS(t). The prerequisite is real, useful guidance, but there is no explicit when-not condition or named alternative for related checks.

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