Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENNoGitHub personal access token for live GitHub integration
CHARLIE_VOICENoSet to 'off' to disable jokes and get plain output

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
charlie_scan_toilA

Scan a repository for toil — the un-fun, load-bearing maintenance work everyone ignores: flaky, skipped, and focused tests; TODO/FIXME/HACK rot; expiring TLS certs; feature flags read but never set; unpinned dependencies; unowned operational scripts; and stray debug statements. Returns a prioritized queue. Set mode='plain' for a flavor-free report.

charlie_did_itA

Record that someone cleared a piece of toil, by its toil_id from a scan. Persists to a local ledger so the invisible work becomes visible. Rescans to resolve the item's title.

charlie_ledgerA

Report the credit ledger for standup or retro: who cleared what toil, the current Champion of the Grease Trap, and how much is still open.

charlie_summaryB

Report the repo's toil budget: total estimated remediation minutes, a debt ratio, an A-E maintainability grade, and counts by kind. Google SRE says keep toil under 50 percent.

charlie_explainA

Explain why a specific finding (by its toil id) is real debt, with evidence and a fix.

charlie_triageB

Return the top-N highest-priority toil items as an action plan for an agent to work through.

charlie_trendC

Record a toil snapshot and report how the toil budget has moved since last time.

Prompts

Interactive templates invoked by user choice

NameDescription
triage_toil

Resources

Contextual data attached and managed by the client

NameDescription
toil_queue_resource

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: scanning for toil, explaining a finding, recording clearance, reporting the ledger, summarizing budget, tracking trends, and triaging priorities. No overlap.

Naming Consistency5/5

All tools follow a consistent 'charlie_verb' pattern with clear action words: scan_toil, explain, did_it, ledger, summary, trend, triage. The naming is predictable and informative.

Tool Count5/5

Seven tools cover the core workflow of toil management without excess. The count is well-scoped for the domain, providing essential functions without unnecessary duplication.

Completeness4/5

The tool set covers discovery, explanation, resolution recording, and reporting. Minor gaps might include a tool to manually add toil items or update details, but the surface is largely complete for typical toil management.

Maintenance

ActivityStale
ResponsivenessNo issues