Paceword Speed Reader

Run reading speed test

run_reading_speed_test

Read-only

Use this when the user wants an original timed reading-speed practice test with comprehension questions. Accepts short, medium, or long passages only. Returns the passage length and four multiple-choice questions with four options each; correct options stay in widget-only metadata. Do not use for medical or learning-disability assessment.

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": {
      "passage_length": "<passage_length>"
    },
    "name": "run_reading_speed_test"
  }
}

Input Schema

Name	Required	Description	Default
`passage_length`	Yes	Original passage length to test, e.g. medium.

Output Schema

Name	Required	Description	Default
`questions`	Yes
`limit_note`	Yes
`word_count`	Yes
`instructions`	Yes
`passage_length`	Yes
`question_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context beyond them: only three passage lengths are accepted, and the correct answers are withheld in widget-only metadata — an important trait an agent could not infer from the schema or annotations alone.

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: trigger first, constraint second, output shape third, with the exclusion last. No sentence is filler, and the most decision-relevant information is front-loaded.

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 one-parameter, read-only tool with an output schema, the description covers trigger, constraint, exclusion, and the non-obvious answer-hiding behavior. The only minor gap is not pointing to the sibling tools for adjacent requests.

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 coverage is 100% and the single parameter is a three-value enum with its own description, so the schema carries the burden. The description's 'short, medium, or long passages only' merely restates the enum with an added exclusivity emphasis rather than adding format or behavior detail.

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 names a specific verb+resource: an 'original timed reading-speed practice test with comprehension questions', which is far more concrete than the title alone and clearly separable from estimate_reading_time or show_speed_reader by the comprehension-question framing. It never names those siblings explicitly, so the differentiation is implicit rather than stated.

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?

It gives an explicit trigger clause ('Use this when the user wants...') plus a clear exclusion ('Do not use for medical or learning-disability assessment'). It does not, however, point at the sibling tools as the correct alternative when the request is a simple time estimate or a speed-reader display, leaving that routing to inference.

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?