Skip to main content
Glama
AIStoryHub

Étincel MCP Server

by AIStoryHub

Audit text for AI writing tells

audit_text
Read-onlyIdempotent

Scan non-fiction for AI-writing tells (banned words, chatbot patterns, structural issues) and get a tiered score with findings and strengths to guide targeted fixes.

Instructions

Deterministically scan a piece of non-fiction text for common AI-writing tells: banned hype vocabulary, chatbot fingerprints, and structural patterns (uniform paragraph length, stacked transitions, em-dash overuse, rule-of-three compulsion, and more), plus this installer's own banned/custom word lists from add_banned_word/add_custom_word (the 'global' list, merged with a style's own list if styleId is given), plus a repo-local .etincelrc/.etincelrc.json/etincel.config.json if one exists at or above the current directory (dictionary as code, reviewable and versioned). Returns a tier (green/yellow/orange/red), a numeric score, specific findings with severity and location, and a strengths signal (specificity density, concrete-vs-abstract ratio, sentence-rhythm variation). Read strengths too, not just findings: it's the counter-signal against fixing every flagged word into flat, sterile prose. Never a silent rewrite. Use this to show the user what's flagged and why, so they stay in control of any change; only rewrite what they ask you to rewrite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to audit.
styleIdNoStyle id (from list_styles) whose own banned/custom word list should merge with the installer's global list. Omit to use only the global list.
registerNoRegister to calibrate strictness against. Defaults to 'general'.
Behavior5/5

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

Annotations already declare read-only and idempotent; description adds determinism, config-file reading, strengths signal, and never-silent-rewrite promise. This enriches behavioral understanding beyond annotation hints.

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?

Dense but efficient paragraph front-loads the core action; every sentence contributes, but length may be slightly overwhelming. Could use paragraph breaks for readability.

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?

With no output schema, description fully explains return values (tier, score, findings, strengths). Also covers config file integration and usage philosophy, making the tool's contract clear.

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 covers all parameters with descriptions (100% coverage). Description reinforces styleId merging and register calibration but adds no new syntactic detail beyond schema.

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?

Clearly states it deterministically scans non-fiction text for AI-writing tells, listing specific patterns and output categories. Distinguishes from sibling tools focused on style management and narrower checks like check_voice_match.

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?

Provides explicit usage context: show the user what's flagged and why, only rewrite on request. Implies a broader audit role versus siblings but doesn't explicitly name alternatives or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIStoryHub/etincel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server