Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PROOFSPEC_CONFIGNoPath to the proofspec.json configuration file. The server reads proofspec.json from the project directory by default.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Proofspec evaluates narrow software claims against constrained evidence. Use proofspec_validate before a run, proofspec_check to create fresh receipts, and proofspec_explain for one claim. Treat unknown, unsupported, blocked, and failed as unverified. A satisfied verifier proves only the configured observation, not the broader quality of a project.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
proofspec_validateB

Validate a Proofspec configuration, including unique IDs and an acyclic claim graph, without checking evidence.

proofspec_checkC

Evaluate every claim, append independently labelled evidence receipts, verify the ledger, and return the complete report.

proofspec_explainC

Evaluate the specification and return one claim with its policy, dependencies, limitations, evidence, and receipts.

proofspec_renderC

Evaluate a specification and render JSON, Markdown, standalone HTML, Mermaid, or SARIF.

Prompts

Interactive templates invoked by user choice

NameDescription
audit-public-claimsConvert public software claims into narrow, executable evidence contracts

Resources

Contextual data attached and managed by the client

NameDescription
schemaProofspec 1 JSON Schema
exampleA complete executable claim specification

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a distinct primary output: validation, full evaluation report, single-claim explanation, and multi-format rendering. However, check, explain, and render all evaluate the specification, so their boundaries overlap somewhat even though the descriptions clarify the differences.

Naming Consistency5/5

All four tools use the same proofspec_ prefix followed by a clear verb: validate, check, explain, render. The naming pattern is fully consistent and predictable.

Tool Count5/5

Four tools is a well-scoped set for a proofspec configuration utility, with each tool covering a distinct operation. There is no obvious bloat or missing core operation at this count.

Completeness4/5

The surface covers validation, full evaluation, per-claim explanation, and rendering across multiple formats, which is strong lifecycle coverage for analysis. A minor gap is the absence of a create/init or edit operation, though the server may intentionally be read-only over existing specifications.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues