Hopi

Word counter

hopi_word_counter

Read-onlyIdempotent

Analyse a block of text and return the word count, character count (with and without spaces), sentence count, paragraph count and an estimated reading time at 225 words per minute. Source: https://hopi.co.uk/word-counter/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	The text to analyse

Output Schema

TableJSON Schema

Name	Required	Description
`words`	No
`summary`	Yes
`sentences`	No
`characters`	No
`paragraphs`	No
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`readingTime`	No
`charactersNoSpaces`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish this as read-only, idempotent, and non-destructive. The description adds useful behavioral detail beyond that, including the exact reading-time assumption of 225 words per minute and the specific set of counts returned, which is more than the structured fields convey.

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 a single, front-loaded sentence that clearly states the action and outputs. The source URL adds provenance but is not operationally necessary for an agent invoking the tool, preventing a perfect 5.

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?

Given the tool's simplicity, one parameter, rich annotations, and existing output schema, the description covers everything an agent needs: what input to provide, what analyses are performed, and the specific outputs returned. No critical operational detail is missing.

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%, with the single 'text' parameter described as 'The text to analyse'. The description's phrase 'block of text' adds no significant semantic detail beyond the schema, so the high-coverage baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Analyse') and resource ('a block of text'), then enumerates the exact return metrics: word count, character counts, sentence count, paragraph count, and reading time. This output list distinguishes it from sibling tools like hopi_character_counter and hopi_reading_time_calculator, which focus on single metrics.

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 implies this is for analysing a block of text, but it gives no explicit guidance on when to choose this tool over its siblings, such as hopi_character_counter or hopi_reading_time_calculator. There are no stated exclusions, prerequisites, or alternative-routing conditions.

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

All Hopi 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?