Skip to main content
Glama

ass_cps

Calculate characters per second for selected ASS subtitle lines and totals to assess reading speed and identify timing issues. Returns per-line CPS, max, and worst index.

Instructions

Characters per second for every selected line plus the totals.

Args: selection: lines to measure; None/[] means every line. doc_id: document id.

Returns: {"doc_id", "count", "lines": [{"index", "kind", "characters", "duration_ms", "cps", "drawing", "start_ms", "end_ms"}], "totals": {"characters", "duration_ms", "average_cps", "max_cps", "worst_index"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idNo
selectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It describes the computed output but does not state whether the tool is read-only, whether it modifies the document, what permissions are needed, or any side effects. This leaves the agent guessing about safety and side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose and then structured into Args and Returns sections. It is appropriately sized, but the Returns block duplicates information already available in the output schema, making it slightly redundant.

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?

Given no annotations and 0% schema description coverage, the description adequately documents the parameters and notes the return shape. However, it omits when to use this tool versus similar siblings and provides no safety or side-effect context, leaving gaps for an agent deciding between related tools.

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?

Schema coverage is 0%, so the description must compensate. It documents both parameters: selection is 'lines to measure' with None/[] meaning every line, and doc_id is the document id. This adds clear meaning beyond the bare schema, though selection's expected type (e.g., indices vs. line objects) remains slightly ambiguous.

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 states a specific metric and scope: characters per second for selected lines plus totals. It distinguishes the tool from a generic stats tool by naming the exact output metric, but it does not explicitly differentiate itself from the similar sibling ass_reading_speed.

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?

The description explains the selection parameter's default behavior but gives no guidance on when to use this tool over alternatives such as ass_reading_speed or ass_stats. No exclusions, prerequisites, or usage context are provided.

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