md-lint
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lint_markdownA | Lint a Markdown file for broken relative links, heading hierarchy, empty links, and common README issues. Local files only. Relative links are checked on disk; external http(s) links are not fetched. |
| lint_markdown_treeA | Lint all Markdown files under a directory (skips node_modules/.git). Local files only. Relative links are checked on disk; external http(s) links are not fetched. |
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 2 tools
The two tools have clearly distinct targets: one lints a single file, the other recursively lints a directory tree. No overlap or ambiguity exists.
Both tool names use the consistent lint_markdown prefix with a clear suffix distinguishing scope. The pattern is predictable and readable.
Two tools cover the core file and directory linting cases, but the count feels slightly thin for the domain; a tool for linting content or configuration might add value.
The surface covers linting individual files and directory trees, which are the primary local operations. Minor gaps like linting a list of files or custom configs exist but are not critical.