Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
docvet_checkA

Run docvet checks on Python files.

Analyzes Python source files for docstring quality issues. Runs all
enabled checks except freshness by default (freshness requires git
context; griffe also excluded when not installed). When *path* is a
directory, only files within that directory tree are checked (not the
entire project). Returns a JSON object with findings, summary
statistics, and optional presence coverage data. Invalid
configuration triggers a structured error response instead of
crashing the server. Input, read, decode, and parse failures report
an incomplete run with unique attempted, analyzed, and failed file counts.
Presence coverage explicitly marks incomplete results, with a null
percentage when no input could be analyzed. Legitimate empty selections
succeed without requiring optional check dependencies or git context.

Args:
    path: Path to a Python file or directory to check.
    checks: Optional list of check names to run. Valid names are
        ``presence``, ``enrichment``, ``freshness``, ``coverage``,
        ``griffe``. Defaults to all except freshness.

Returns:
    JSON string with ``findings``, ``summary``, and optionally
    ``presence_coverage`` keys. Returns an ``error`` key on
    invalid path, unknown check name, or malformed configuration.
    Call docvet_rules() for per-rule fix guidance and format examples.
docvet_rulesB

List all available docvet rules with fix guidance.

Returns the complete rule catalog with rule name, associated check
module, human-readable description, category (required or
recommended), prescriptive fix guidance, and a format example.

Returns:
    JSON string with a ``rules`` array containing objects with
    ``name``, ``check``, ``description``, ``category``,
    ``guidance``, and ``fix_example`` keys.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: docvet_rules is a read-only catalog lookup while docvet_check executes analysis on files. An agent can easily tell which to call for discovery versus execution.

Naming Consistency4/5

Both tools share the docvet_ prefix, giving a predictable namespace and readable names. The slight verb/noun mismatch between docvet_rules (noun) and docvet_check (verb) is a minor deviation but still coherent.

Tool Count3/5

Two tools is on the thin side for the domain; a linter commonly benefits from separate config, fix, or freshness-context tools. It works but feels under-scoped for the apparent feature set (presence, enrichment, coverage, griffe, freshness).

Completeness4/5

Discovery (rules) and execution (check) cover the core linting lifecycle, with rules providing fix guidance. However there is no auto-fix operation despite the emphasis on fix guidance, and freshness/git-context handling is bundled rather than exposed, a minor gap.

Maintenance

ActivityMaintained
ResponsivenessResponsive