Skip to main content
Glama

Bilingual reading time estimate

bpj_reading_length_estimate
Read-onlyIdempotent

Estimate reading time using separate Chinese character and other word counts plus your chosen speeds.

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": {
      "content": "<content>",
      "hanPerMinute": "<hanPerMinute>",
      "wordsPerMinute": "<wordsPerMinute>"
    },
    "name": "bpj_reading_length_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
hanPerMinuteYes
wordsPerMinuteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one real behavioral fact beyond that: the caller chooses the speeds, so results are caller-dependent rather than using fixed defaults. It says nothing about the 12,000-character cap, truncation behavior, or the shape/units of the returned estimate.

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?

A single front-loaded sentence with no filler; nothing is wasted. The trailing "plus your chosen speeds" is slightly informal but carries the key signal that rates are user-controlled.

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?

For a simple three-parameter estimator with no output schema, the definition is serviceable but leaves the return contract unspecified — a caller cannot tell whether the answer is in minutes, seconds, or a structured breakdown. That gap matters more here precisely because no output schema exists to fill it.

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 0%, so baseline expectations rise, but the schema itself supplies titles and min/max on all three parameters. The description's contribution is explaining that Chinese characters and other words are counted in separate buckets, which the parameter names only partially convey; it adds no clarity on output units (minutes vs seconds) or how mixed text is segmented.

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?

Specific verb+resource: "Estimate reading time" with the counting model named ("separate Chinese character and other word counts"). It goes beyond a bare restatement of the name by explaining the dual-bucket counting approach, though it does not explicitly position itself against any sibling utility.

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 stated: the tool is a pure calculator whose inputs (body text plus caller-supplied rates) make its role obvious. There is no explicit when-to-use, no precondition, and no exclusion, but for a stateless estimate tool little guidance is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.