typetrace
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPETRACE_CACHE | No | Directory where the indexes live. Defaults to `~/.cache/typetrace/`. | ~/.cache/typetrace/ |
| TYPETRACE_MODEL_DIR | No | Directory where the embedding model is stored. Defaults to `~/.cache/typetrace/models/`. | ~/.cache/typetrace/models/ |
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 |
|---|---|
| find_relevant_codeA | Find where something is implemented in this codebase. Returns a short list of functions/methods with file:line ranges and signatures (and, when known, their direct callers, callees and handlers). Read the ranges you need. |
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 1 tool
With only one tool in the set, there is no possibility of misselection or overlap with a sibling tool. The tool's purpose (locate an implementation and return file:line ranges with signatures) is stated clearly enough that an agent knows exactly when to call it.
The single name find_relevant_code follows a clear verb_adjective_noun snake_case convention and reads naturally. There are no competing conventions to conflict with, so consistency is trivially satisfied.
A code-exploration server exposing exactly one tool is thin for the apparent scope; search without companion read/list operations leaves the workflow dependent on capabilities the server does not provide. The tool itself earns its place, but the surface is under-scoped rather than well-scoped.
Discovery is the only operation offered: there is no way to read a file, fetch a symbol definition, or list a directory, even though the description tells the agent to 'read the ranges you need' without supplying a means to do so. This is a significant gap that will cause dead ends for any task beyond initial localization.