SciTrace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCITRACE_DB | No | Path to the SQLite database file. Defaults to ~/.scitrace/traces.db | ~/.scitrace/traces.db |
| SCITRACE_OUTPUT | No | Directory for visualization output. Defaults to current working directory. | . |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_traceA | Record a reasoning step from the agent's execution. Each step has a type (hypothesis/experiment/analysis/conclusion/verification/backtrack), an optional parent_id to build a reasoning DAG, and optional artifact file paths. |
| query_traceA | Query historical reasoning steps. Filter by trace_id and/or type. Returns steps ordered by most recent first, up to the specified limit. |
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 2 tools
build_trace records a new reasoning step, while query_trace retrieves existing steps. Their purposes are clearly distinct, with no overlap in functionality.
Both tools follow the consistent verb_noun pattern (build_trace, query_trace), making their actions predictable and easily understood.
With only 2 tools, the set is minimal, but each tool is essential for the server's stated purpose of recording and querying reasoning traces. This falls at the borderline of being too thin.
The server covers the core write (build_trace) and read (query_trace) operations for reasoning traces. Missing update/delete functionality is a minor gap, but acceptable for an append-only trace logging context.