circe-mcp
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 | Check text against the Circe Editorial Standard (CES) v0.3. Returns each violation with its rule ID, severity, confidence, line and column, the matched text, a message, and a suggested fix. Overlapping violations are reported once, with the others listed under 'related'. |
| list_rulesA | List the CES rules this server enforces, with ID, name, severity, and a one-line description. Optional rules are marked. |
| explain_ruleA | Show the full text of one CES rule: the pattern, why it is a tell, the replacement strategy, exceptions, a before/after example, and the tokens the checker uses. |
| fix_textA | Apply the safe fixes to a text: em dashes become commas, and reflexive hedges and hollow intensifiers are deleted. Returns the fixed text, the list of edits, and the violations left for the writer. |
| measure_textA | Report statistics about a text with no verdict: sentence lengths and rhythm per paragraph, opener echo, specificity density (CES-V-004), paragraph density (CES-S-002), and over-enthusiasm signals (CES-V-005). |
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 5 tools
Each tool has a clearly distinct role: check_text finds violations, measure_text reports statistics with no verdict, fix_text applies safe fixes, list_rules enumerates rules, and explain_rule details a single rule. The check_text/measure_text boundary is explicitly clarified by 'no verdict' vs violation reporting, leaving no real overlap.
All five tools follow a consistent verb_noun snake_case pattern (check_text, fix_text, measure_text, list_rules, explain_rule). Verb pairing with noun reads predictably across the set.
Five tools is well-scoped for an editorial-linting server, covering the natural verbs (check, fix, measure, list, explain) without redundancy. Each tool earns its place in the workflow.
The core lifecycle is covered: discovery (list_rules, explain_rule), analysis (check_text, measure_text), and remediation (fix_text). Minor gaps exist, such as batch/file-level checking or rule configuration, but agents can work around them.