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
prufgate_fast_scanA

Run engines 1-5 (anti-fabrication, test integrity, diff guard, contract guard, static BOLA) on changed files.

prufgate_full_scanA

Run engines 1-5 on the whole workspace plus the diff reviewer; adds the live BOLA probe only when target_url is set.

prufgate_anti_fabricationC

Engine 1: canned fallbacks, simulated return values, stub handlers and other fabricated production logic.

prufgate_test_auditC

Engine 2: zero-assertion tests, tautologies, self-mocked units and weakened assertions.

prufgate_diff_guardC

Engine 3: skipped tests, suppression comments, unsafe casts and weakened lint/CI config added in the diff.

prufgate_contract_checkC

Engine 4: undeclared or hallucinated imports, undocumented environment variables and frontend/backend route mismatches.

prufgate_bola_checkB

Engine 5: routes and queries without auth or tenant scoping; the live two-token probe runs only when target_url is set.

prufgate_reviewC

Engine 6: deterministic review of the diff against base_ref (default: resolved like prufgate check --changed).

prufgate_summaryA

Read the last SARIF/Markdown report written by ./prufgate.sh without running a scan.

prufgate_explainA

What a rule catches, how to fix it, and how to record a false positive. Pass the rule ID a finding names.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Each tool has a distinct role: individual engines, composite scans, rule explanation, and report reading. There is minor overlap between fast_scan/full_scan and the engine-specific tools, but the descriptions clarify scope as changed files vs whole workspace vs single engine.

Naming Consistency5/5

All ten tools use the same prufgate_ prefix and snake_case formatting, with no mixed conventions. Whether the name is action-oriented or an engine label, it follows the same predictable namespace pattern.

Tool Count5/5

Ten tools map cleanly to six engines plus aggregate scans, explanation, and summary reporting. The count is well-scoped, with no obvious filler or redundant tools.

Completeness4/5

The surface covers individual engines 1-6, aggregate scans, rule explanation, and summary report reading. Minor gaps remain around programmatic findings access, false-positive recording, and rule listing, but core scanning workflows are covered.

Maintenance

ActivityNo data
ResponsivenessOutdated data