Skip to main content
Glama
baokhang83

fluencydrift-mcp

by baokhang83

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
list_architectural_recordsA

List the fluencyloop-tracked repo's resolved architectural records (concepts, principles, decisions).

check_driftA

Compare the repo's recorded architecture against reality and report structured drift findings.

explain_recordA

Explain one architectural record by name.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool serves a distinct function: listing all records, checking drift, and explaining a specific record. No overlapping purposes, so an agent can easily select the right tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores: list_architectural_records, check_drift, explain_record. This is uniform and predictable.

Tool Count5/5

Three tools is a well-scoped size for a focused drift-checking utility. Each tool is essential and there is no bloat or sense of missing critical functionality.

Completeness5/5

For its stated purpose of monitoring architectural drift, the set covers the full workflow: list records to see what exists, explain a record to understand it, and check drift to identify mismatches from reality. No apparent gaps or dead ends.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive