Skip to main content
Glama
tosssssy

debug-thinking

by tosssssy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

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
debug_thinkingA

Graph-based debugging knowledge management system. Helps track debugging process systematically and retrieve past solutions.

Use this tool when:

  • User reports an error or bug that needs systematic investigation

  • You need to document your debugging approach for complex issues

  • You want to check if similar problems were solved before

  • Building a knowledge base of debugging patterns

Actions:

  1. CREATE - Add nodes to the debugging graph

    • nodeType: problem|hypothesis|experiment|observation|learning|solution

    • content: Description of the node

    • parentId: Optional parent node for automatic edge creation

    • metadata: Optional tags, confidence scores, etc.

  2. CONNECT - Link nodes with relationships

    • from/to: Node IDs to connect

    • type: decomposes|hypothesizes|tests|produces|learns|contradicts|supports|solves

    • strength: 0-1 relationship strength

  3. QUERY - Search and analyze the graph

    • queryType: similar-problems|recent-activity

    • parameters: pattern (search text), limit, minSimilarity

Example workflow:

  • CREATE problem "TypeError: Cannot read property 'x' of undefined"

  • CREATE hypothesis "Missing null check in async operation"

  • CREATE experiment "Add optional chaining operator"

  • CREATE observation "Error resolved"

  • QUERY similar-problems with pattern "TypeError undefined"

Data persists in ~/.debug-thinking-mcp/

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.9/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no ambiguity between tools. The tool's multiple actions are clearly separated within it.

Naming Consistency5/5

The single tool name 'debug_thinking' is consistent and descriptive. No naming inconsistencies exist.

Tool Count5/5

One tool is appropriate for this domain as it encapsulates all necessary operations (create, connect, query) in a cohesive interface for debugging knowledge management.

Completeness4/5

The tool covers core actions like creating nodes, connecting them, and querying. Missing explicit update/delete operations for nodes, but the graph-based approach may rely on recreation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources