syncause-debug-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your API key from syn-cause.com/dashboard |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_debug_tracesB | Entry point for troubleshooting. Search for relevant error logs, slow queries, or specific business ID execution traces based on user questions or error descriptions. |
| get_trace_insightA | Get a complete lifecycle report for a single request, including call tree skeleton, key SQL summaries, and exception logs. |
| inspect_method_snapshotB | Deep dive into a specific method for a given request, returning precise input/output parameters, local variables, and logs generated within its scope. |
| diff_trace_executionB | Compare the execution paths and data differences between two requests (usually one successful and one failed) to identify the root cause of bugs. |
| setup_projectA | Initialize or retrieve a specific project's configuration by its path. Use this when you have a local project path and need its 'projectId'. If you want to see already configured projects, use 'get_project_list' first. |
| get_project_listA | List all projects that have already been initialized. This is the preferred way to discover available 'projectId's and their corresponding paths without re-initializing them. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct level of the tracing workflow: discovery (search_debug_traces), request-level report (get_trace_insight), method-level drill-down (inspect_method_snapshot), comparison (diff_trace_execution), and project config (setup_project/get_project_list). The only mild overlap is between search_debug_traces and get_trace_insight, since both surface logs/errors, but the descriptions clarify search is the entry point and insight is a full lifecycle report.
All names follow a snake_case verb_noun pattern (get_trace_insight, search_debug_traces, inspect_method_snapshot, diff_trace_execution, setup_project, get_project_list). Minor deviation: 'diff' and 'setup' are less standard verbs than get/search/inspect, and project tools split verbs (get vs setup) for related concepts, but overall the convention is predictable.
Six tools is well-scoped for a trace-debugging server: two for project setup/discovery and four covering the search-to-diagnosis-to-comparison flow. No tool appears redundant or filler.
The core lifecycle (discover project, search traces, inspect request and method detail, diff two requests) is fully covered. Minor gaps exist around project config lifecycle (no removal/reset of an initialized project) and no way to list or browse recent traces without a search query, but agents can work around these.