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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_evidence_bundleB

Creates a new evidence bundle for a task and workspace with in_progress status.

capture_git_evidenceB

Safely inspects and captures Git state (status, branch, HEAD commit, diff check) without mutating the repo.

record_command_resultA

Records the execution result of a command previously run by an agent (does not execute shell commands).

snapshot_filesB

Computes SHA-256 hashes and file sizes for files strictly inside the workspace. Rejects sensitive files.

add_assertionB

Links a stated claim to one or more supporting evidence IDs. Rejects assertions with zero evidence.

verify_evidence_bundleA

Re-checks Git state and file hashes against live workspace. Returns verified, stale, or failed status.

export_evidence_reportB

Produces a comprehensive evidence report in Markdown or JSON format suitable for pull requests, issues, or handoffs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct action in the evidence lifecycle: create bundle, capture Git state, snapshot files, record command results, add assertions, verify evidence, and export reports. The closest overlap is capture_git_evidence versus verify_evidence_bundle, but one captures live Git state while the other re-checks stored evidence against the workspace, so the boundary is clear.

Naming Consistency5/5

All tool names use snake_case with a verb-first pattern: add_assertion, verify_evidence_bundle, export_evidence_report, create_evidence_bundle, capture_git_evidence, record_command_result, and snapshot_files. The convention is consistent throughout, with only natural variation in object length.

Tool Count5/5

Seven tools is well within the ideal range for a focused server and each tool supports a clear stage of the evidence workflow. There are no obviously redundant or filler tools.

Completeness4/5

The surface covers bundle creation, evidence capture from Git, files, and command results, assertion linking, verification, and report export. Minor gaps remain: there is no list/get operation for existing bundles or stored evidence/assertions, and no update/delete/archive path, which may limit discovery and maintenance for long-lived or multiple bundles.

Maintenance

ActivityMaintained
ResponsivenessNo issues