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.

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.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: docvet_check executes checks and returns findings, while docvet_rules lists rule metadata and fix guidance. There is no overlap, and the check tool explicitly points to the rules tool for next steps.

Naming Consistency4/5

Both tools use a consistent snake_case pattern with the shared 'docvet_' prefix. However, the second parts differ in form ('check' is an action, 'rules' is a resource), which is a minor deviation from a pure verb_noun convention.

Tool Count4/5

Two tools are slightly under the typical 3-15 range, but each earns its place in this narrow, well-scoped docstring-checking domain. The check tool is feature-rich, so the set does not feel arbitrarily thin.

Completeness4/5

The core workflow—run checks, then look up rule guidance—is fully covered, and the check tool handles configuration errors gracefully. Minor gaps exist, such as no direct auto-fix or fix-application tool, but these are not essential for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessResponsive