Skip to main content
Glama
Sign In
WSC - Writing Style Checker

WSC - Writing Style Checker

by theserverlessdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check a file for writing style issues

check_file
Read-only

Analyze a UTF-8 file from disk for writing style issues including weasel words, passive voice, and hedging. Returns a line-and-column report.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "check_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute or relative path to the file to analyze; read as UTF-8
configNoOptional config (same schema as .wscrc.json); when set, auto-discovery of .wscrc.json is skipped

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.2.2
    • addedInput schema / properties / config / additionalProperties
      Added value: +{}
    • changedInput schema / properties / config / description
      Previous value: -"Optional WscConfig JSON object (overrides auto-discovered .wscrc.json)"New value: +"Optional config (same schema as .wscrc.json); when set, auto-discovery of .wscrc.json is skipped"
    • addedInput schema / properties / config / propertyNames
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / config / type
      Added value: +"object"
    • changedInput schema / properties / path / description
      Previous value: -"Path to the file to analyze"New value: +"Absolute or relative path to the file to analyze; read as UTF-8"
  2. First observedv2.2.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations set readOnlyHint=true, and the description reinforces 'Read-only: the file is never modified.' It adds important details like Markdown masking for code blocks/tables, auto-discovery of config, and error conditions for unreadable/oversized files. No contradictions with annotations.

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 approximately 100 words, every sentence serves a purpose. Front-loaded with the core action, then adds behavioral semantics and usage guidance without redundancy.

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?

Despite no output schema, the description adequately explains the return format (same line-and-column report as check_text) and error conditions. Covers config auto-discovery, file size limit, and Markdown masking, making the tool's behavior fully understood.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (100% coverage). The description adds value by explaining path must be UTF-8 and that setting config disables auto-discovery, which enriches the schema information.

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?

Explicitly states the tool reads a file from local disk and analyzes for writing style issues, directly distinguishing it from check_text for inline text. The verb 'read and analyze' clearly specifies the action on the resource.

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?

Provides explicit guidance: 'Use when the text lives on disk; use check_text for text already in the conversation.' This clearly defines appropriate use cases and the alternative tool.

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

Deploy Server

Other Tools