WSC - Writing Style Checker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_textA | Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory, never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. Use this for text already in the conversation; use check_file for files on disk. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates. |
| fix_duplicatesA | Remove duplicate adjacent words (case-insensitive, including across line breaks) and return the cleaned text plus the list of words that were removed. Read-only with no side effects: the fix is returned in the response, nothing is written anywhere. Use after check_text or check_file reports duplicate words; other issue types are report-only and have no auto-fix. |
| list_word_listsA | Return every detector word/phrase list with its entry count, config key, and sample entries, plus a link to the full browsable library. Read-only, takes no parameters, and returns the same catalog for a given release. Use it to see what the detectors match before tuning a config for check_text or check_file; not needed for ordinary checking. |
| check_fileA | Read a UTF-8 file from local disk and analyze it for the same writing style issues as check_text (weasel words, passive voice, hedging, AI tells, and more). Read-only: the file is never modified, and Markdown files are automatically masked so code blocks and tables are not linted as prose. A .wscrc.json config is auto-discovered from the file's directory upward unless config is passed explicitly. Returns the same line-and-column report as check_text, or an error message for unreadable or oversized (over 100,000 characters) files. Use when the text lives on disk; use check_text for text already in the conversation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: check_file vs check_text differ by input source, fix_duplicates is for fixing a specific issue, and list_word_lists provides reference data. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (check_file, check_text, fix_duplicates, list_word_lists), making the API predictable.
With 4 tools, the server is well-scoped for a writing style checker: two input methods for analysis, one fix action, and one list action. Not overly sparse or heavy.
The tool surface covers core checking and duplicate removal, but lacks auto-fix for other issue types (e.g., weasel words, passive voice). Users must manually edit text after reports, which is a minor gap.