Paceword Speed Reader

Show speed reader

show_speed_reader

Read-only

Use this when the user wants to practice reading supplied text one word at a time. Accepts up to 20,000 characters, 100 to 1,000 words per minute, and 1 to 4 words per flash. Returns the word count and scheduled reading time; it is a training aid and does not measure comprehension.

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": {
      "text": "<text>"
    },
    "name": "show_speed_reader"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Text to pace in the reader, up to 20,000 characters, e.g. The harbor lights returned after the rain.
`words_per_flash`	No	Words shown together on each flash from 1 to 4, e.g. 1.
`words_per_minute`	No	Pacing speed from 100 to 1,000 words per minute, e.g. 350.

Output Schema

Name	Required	Description	Default
`limit_note`	Yes
`word_count`	Yes
`scheduled_time`	Yes
`words_per_flash`	Yes
`words_per_minute`	Yes
`scheduled_time_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's job is to add context — and it does: it discloses the input caps, that it returns word count and scheduled reading time, and that it does not measure comprehension. Only pagination or presentation details remain unstated, which is minor.

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 the usage trigger, followed by constraints and return behavior. No sentence is redundant and nothing is buried.

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

Completeness5/5

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

For a three-parameter read-only tool with full schema coverage and an output schema, the description covers trigger, limits, return values, and scope limitations. An agent has everything needed to select and invoke it correctly.

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 all three parameters with their ranges and examples are already documented. The description restates the same ranges (20,000 chars, 100–1,000 wpm, 1–4 words per flash) without adding meaning beyond the schema, making the baseline 3 appropriate.

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: pacing supplied text one word at a time to practice reading. It implicitly separates itself from the sibling run_reading_speed_test by noting it 'is a training aid and does not measure comprehension,' though it never names siblings explicitly.

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

Usage Guidelines4/5

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

'Use this when the user wants to practice reading supplied text one word at a time' gives a clear trigger condition, and the closing caveat bounds the tool's role. It stops short of naming estimate_reading_time as the alternative for pure time estimation.

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

All Paceword Speed Reader tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?