fixgraph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIXGRAPH_API_KEY | No | API key for FixGraph. Search is free and requires no key. To submit fixes, get a key at fixgraph.netlify.app. |
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 |
|---|---|
| fixgraph_searchB | Search FixGraph for engineering fixes. Returns matching issues with trust scores and fix counts. |
| fixgraph_get_fixesA | Get all verified fixes for a specific FixGraph issue by its ID or slug. |
| fixgraph_submit_fixB | Submit a new fix to FixGraph. Requires FIXGRAPH_API_KEY env var. |
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 3 tools
Each tool has a distinct purpose: searching for issues, retrieving fixes for a specific issue, and submitting a new fix. There is no overlap or ambiguity.
Tools follow the 'fixgraph_<verb>' pattern, but 'fixgraph_search' lacks a noun after the verb while the others include one. This minor inconsistency does not impede readability.
With only three tools, the set is slightly thin but appropriate for a focused service that allows search, retrieval, and submission of fixes. It is not under-scoped.
The tools cover basic operations (search, get, create) but lack update and delete functionality. This is a noticeable gap for full lifecycle management.