Skip to main content
Glama

Moltline Creator Studio

by com.moltlinestudio

Reading Time

reading_time
Read-onlyIdempotent

Estimate reading and speaking time plus basic content stats. FREE.

Typical input {"text": ""} returns {"words": 1200, "reading_minutes": 5.2, "speaking_minutes": 8.6, "paragraphs": 14, "fit": "newsletter/blog"}.

Use when length and pacing are the question. Not for writing quality or grade level (analyze_writing). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wpmNoSilent reading speed in words per minute; values below 60 are treated as 60. Default 230.
textYesThe content to measure, plain text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable context: 'Every call is read-only and idempotent, so after correcting the input it is always safe to retry.' It also discloses error behavior (returns error object instead of protocol error). No contradiction.

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?

Concise at ~100 words, efficiently structured: purpose, example, usage guidance, error handling, idempotency note. Every sentence serves a purpose, and the most important information is front-loaded.

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?

The description covers all necessary aspects: purpose, typical usage, when to use/not use, error behavior, and idempotency. Given the presence of an output schema (not shown), no further return value details are needed. Complete for this tool's complexity.

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%, so the baseline is 3. The description does not add new semantic meaning for parameters beyond what the schema provides. The example shows typical input but doesn't explain parameter details or constraints.

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 clearly states the tool's purpose with a specific verb ('estimate') and resource ('reading and speaking time plus basic content stats'). It provides a concrete example and distinguishes from the sibling 'analyze_writing' tool.

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

Usage Guidelines5/5

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

Explicitly states when to use ('Use when length and pacing are the question') and when not to use ('Not for writing quality or grade level'), naming the alternative tool. Also describes error handling behavior and retry safety.

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

All Moltline Creator Studio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct function: writing analysis, headline ranking, reading time, social length check, product listing, free skill retrieval, full product retrieval, and paid skill retrieval. There is no overlap, and the descriptions clearly differentiate them.

Naming Consistency3/5

Tool names use mixed conventions: imperative verbs (get_, list_) for product tools, but descriptive nouns for writing tools (headline_analyzer, reading_time, social_length_check). While not chaotic, the lack of a uniform pattern could cause minor confusion.

Tool Count5/5

With 8 tools covering two related areas (writing analysis and product catalog), the count is well-scoped. Each tool serves a clear purpose without redundancy, fitting the server's 'creator' theme.

Completeness4/5

The writing tools cover major content needs (draft quality, headlines, reading time, platform limits). The product tools provide complete read-only access to the catalog. A minor gap is the lack of search or filtering, but list_products returns all 20 products, which is adequate.

Resources