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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
diffci_changed_filesA

List staged, unstaged and non-ignored untracked changed paths relative to HEAD, with a snapshot identity. Builds no dependency graph and runs no tests.

diffci_select_testsA

Inspect current staged, unstaged and non-ignored untracked changes and return a snapshot-bound affected-test plan and fallback reasons. Runs no tests; a plan is not a passing receipt.

diffci_explain_selectionA

Inspect current staged, unstaged and non-ignored untracked changes and return a snapshot-bound affected-test plan and fallback reasons. Runs no tests; a plan is not a passing receipt.

diffci_run_affected_testsC

Reanalyze and verify the current working-tree snapshot with affected tests or conservative full fallback. Required CI remains authoritative.

diffci_verifyA

Verify a clean commit range and return a receipt bound to the checked-out head commit. Resolves the CI event range automatically when base and head are omitted.

diffci_verify_changedB

Verify the current staged, unstaged, and non-ignored untracked changes. Fails closed unless the exact working-tree snapshot passes selected or full fallback verification.

diffci_checkB

Analyze the repository, run inferred full and selected test commands when available, and report paired runtime. No report is uploaded. Optional aggregate telemetry follows the user's saved consent; DIFFCI_NO_SEND=1 overrides it.

diffci_initB

Seed a repository with DiffCI agent instruction files, MCP server configs, the diffci-verify skill and the pre-push hook.

diffci_verify_workflowC

Check that a DiffCI GitHub Actions job cannot affect the rest of CI.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 9 tools

Disambiguation2/5

diffci_select_tests and diffci_explain_selection have essentially identical descriptions (both return a snapshot-bound affected-test plan with fallback reasons and run no tests), giving an agent no basis to choose between them. Additionally, diffci_check, diffci_run_affected_tests and diffci_verify_changed all operate on the working tree with subtly different semantics (paired runtime vs. snapshot verification vs. fail-closed receipt) that are easy to conflate.

Naming Consistency4/5

All names use a consistent diffci_ prefix and snake_case, so the surface reads predictably. Minor deviations exist: diffci_changed_files is a noun phrase rather than a verb, and the same selection behavior is named with two unrelated verbs (select_tests vs. explain_selection), but the overall form is uniform.

Tool Count4/5

Nine tools is comfortably within a well-scoped range for a diff-based test-selection and verification server. The count would be ideal if the duplicated selection tool were merged, but nothing feels bloated.

Completeness4/5

The lifecycle is well covered: change discovery, plan/selection, affected-test execution, commit-range verification, working-tree verification, CI workflow validation and repo seeding. Minor gaps exist around configuring or inspecting the test-mapping/coverage model and uninstall/reset operations, but core agent workflows have no dead ends.

Maintenance

ActivityActive
ResponsivenessMixed handling