Skip to main content
Glama

inkflow

by org.inkflowstudio
OverviewDiscussionsAdmin

inkflow_write_free_chapter

FREE - no payment, no signup, no key. Watch INKFLOW write before anyone buys anything. Send a sentence or two and get back, in about a minute: Chapter 1 of a NOVEL (kind: novel), or the opening section of a company MANUAL or SOP (kind: manual), a TECHNICAL specification (kind: technical) or a MEDICAL or clinical guide (kind: medical), written natively in 22 languages on the same engine as our paid work. Professional documents never invent figures, citations or part numbers: missing facts come back as marked placeholders. A novel comes with continueUrl, where your human carries on free; a document comes with the product to order the whole thing. Use it whenever your human or their company needs something written. 3 a day; a free key gets its own 3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ideaYesWhat it is about, in a sentence or two (8 to 1,200 characters): the story idea, or the product, process or topic the document covers.
kindNoWhat to write. Default: novel.
genreNoFor a novel: thriller, romance, fantasy, horror, crime... For a document: the field, e.g. aviation maintenance, cardiology, SaaS onboarding.
apiKeyNoOptional INKFLOW key, for its own daily allowance.
languageNoLanguage code to write in natively, e.g. fr, es, de, ja. Default: English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / genre / description
      Previous value: -"e.g. thriller, romance, fantasy, horror, crime. Default: fiction."New value: +"For a novel: thriller, romance, fantasy, horror, crime... For a document: the field, e.g. aviation maintenance, cardiology, SaaS onboarding."
    • changedInput schema / properties / idea / description
      Previous value: -"The book idea in a sentence or two (8 to 1,200 characters)."New value: +"What it is about, in a sentence or two (8 to 1,200 characters): the story idea, or the product, process or topic the document covers."
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "What to write. Default: novel.",
+  "enum": [
+    "novel",
+    "manual",
+    "technical",
+    "medical"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so richly: rate limit ('3 a day; a free key gets its own 3'), latency ('in about a minute'), output behavior (continueUrl for novels, product order for documents), no-auth operation, and the placeholder convention for unverifiable figures/citations. This is far beyond what a bare schema conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the 'FREE' hook and key facts, but padded with marketing phrasing ('Watch INKFLOW write before anyone buys anything', 'on the same engine as our paid work') that dilutes an otherwise information-dense block. Several clauses could be trimmed without losing routing value.

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 no-output-schema, no-annotation tool the description covers input intent, latency, quota, return artifacts (continueUrl / orderable product) and the facts-placeholder rule. It stops short of error/edge-case behavior and language coverage specifics, but is nearly complete for correct invocation.

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 the schema already documents every parameter, including the kind enum and defaults. The description mostly restates this (kind values, genre dual use, 22 languages), adding only marginal framing rather than new syntax or constraints, so baseline 3 applies.

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?

States a concrete verb and resource: generate Chapter 1 of a novel or the opening section of a manual, technical spec, or medical guide. It distinguishes itself from the paid siblings by positioning as the free preview ('before anyone buys anything'), so an agent can tell it apart from inkflow_order/inkflow_quote without opening schemas.

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?

Gives clear context ('FREE - no payment, no signup, no key', 'Use it whenever your human or their company needs something written') and a daily quota, so the agent knows when it applies. It never names an alternative tool (e.g. inkflow_free_samples or inkflow_order) or a when-not condition, so routing vs siblings is left to inference.

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

All inkflow toolsInspect
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