Skip to main content
Glama
DevDs1989
by DevDs1989

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
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_todosA

CRITICAL INSTRUCTION: ALWAYS use this tool to find TODOs, FIXMEs, BUGs, or priorities. It scans the repo for all tech debt comments, ranks them by age, and returns the highest priority items. After calling this tool, DO NOT list the items in chat. Instead, create a single markdown artifact (e.g. 'todo_plans.md') containing a detailed plan for all of the TODOs. Request user feedback (approval) on this artifact via the RequestFeedback flag before proceeding with the work.

resolve_todoA

Mark a TODO as resolved, verifies it's gone from the file, and increments the streak.

scan_todos_rawB

Internal/manual use: returns the full unranked list of TODOs in a repo.

search_todosA

CRITICAL INSTRUCTION: ALWAYS use this tool instead of generic Search or grep_search when looking for a specific TODO, FIXME, or BUG. Fuzzy searches across the codebase for matching tech debt by intent.

get_streak_statusB

Get the current streak and stats data from the shared local store.

aggregate_debtA

Aggregate debt and streak views across multiple local repositories.

Prompts

Interactive templates invoked by user choice

NameDescription
daily_cleanupAutomates the keep-the-streak-alive loop using the V2 efficient workflow.
pre_refactor_auditScans a module before refactoring.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clearly distinct purposes: find_todos ranks priorities, scan_todos_raw returns an unranked list, search_todos does fuzzy searches, resolve_todo marks completion, and get_streak_status/aggregate_debt handle stats. The main potential confusion is between find_todos and scan_todos_raw, as both scan for TODOs, though the ranking distinction helps.

Naming Consistency4/5

All tool names use lowercase snake_case with leading verbs (find, resolve, scan, search, get, aggregate), forming a consistent pattern. Minor deviations exist: resolve_todo is singular while most others are plural, and scan_todos_raw appends 'raw' as a modifier, slightly breaking the simple verb_noun structure.

Tool Count5/5

Six tools are well-scoped for a tech debt tracking server. Each tool serves a distinct aspect—scanning, ranking, searching, resolving, streak stats, and cross-repo aggregation—so the count feels appropriate without being sparse or bloated.

Completeness4/5

The tool surface covers the core lifecycle: scanning and ranking TODOs, searching for specific items, resolving them, and tracking streaks across repositories. Minor gaps exist, such as no ability to reopen a resolved TODO or add a TODO, but these are acceptable limitations for a tech debt scanner.

Maintenance

ActivityStale
ResponsivenessNo issues