grammar-police
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_grammarA | Check and correct English grammar in the provided text. Returns corrections in a structured format. When you receive the text, analyze it for grammar errors and respond with:
IGNORE: Capitalization, punctuation, technical terms/variable names, error/warning logs. |
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 1 tool
There is only one tool, so there are no overlapping purposes to confuse. An agent can unambiguously select check_grammar for any grammar-related request.
The single tool name 'check_grammar' follows a clean verb_noun convention and accurately reflects its function. With only one tool, there are no inconsistent naming patterns to weigh against it.
A single tool is minimal and, by the rubric, feels thin for a server-level surface. However, grammar checking is a narrow domain, so the count is borderline rather than an extreme mismatch.
The tool covers both detection and correction of grammar errors and returns a structured result, including an explicit no-errors case. No obvious operations are missing for the stated grammar-checking purpose.