Skip to main content
Glama

detect_clipping

Measure text bounds and clipping ancestors at each scene midpoint in Chrome to identify layout clipping, excluding screenshot/video text and cleaning temporary QA files.

Instructions

Measure actual composition text bounds and clipping ancestors in Chrome at each scene midpoint; excludes text inside screenshots/video. Temporary QA files are cleaned up.

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": {
      "timeline": "<timeline>"
    },
    "name": "detect_clipping"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The description adds real context beyond annotations: it operates in Chrome, samples at scene midpoints, excludes text rendered inside screenshots/video, and creates temporary QA files that are cleaned up — the latter explains why readOnlyHint is false despite being a measurement tool. It does not mention failure modes or whether a browser must already be running.

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 with no filler; the measuring scope, the midpoint sampling rule, the exclusion, and the cleanup side effect are all front-loaded and each clause carries 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 tool's behavior and side effects are reasonably covered and an output schema handles results, but for a one-shot detection tool the required 'timeline' input is entirely undocumented, leaving an agent unable to construct a correct call without trial and error.

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?

There is one required parameter, 'timeline', with 0% schema description coverage, and the description never explains what it is (project identifier, timeline file, scene list) or its expected format. With output schema present the return values need no explanation, but the sole input remains opaque.

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: measure composition text bounds and clipping ancestors in Chrome at each scene midpoint. That is far more informative than the name alone and implies a QA/detection role distinct from capture or render tools, though it does not explicitly contrast itself with siblings like analyze_rendered_frames or generate_quality_report.

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 only implied by the phrase 'at each scene midpoint' and the exclusion of screenshot/video text; there is no explicit statement of when to run this instead of frame or quality analysis tools, and no stated prerequisites.

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