FixFlow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIXFLOW_MODEL | No | Model name to use, e.g. openai/gpt-oss-120b. | |
| OPENAI_API_KEY | No | OpenAI API key used when FIXFLOW_PROVIDER=openai; also used for Groq OpenAI-compatible API keys, e.g. gsk_... | |
| OPENAI_BASE_URL | No | Base URL for an OpenAI-compatible API, e.g. https://api.groq.com/openai/v1 for Groq. | |
| FIXFLOW_PROVIDER | No | Selects the LLM provider. Set to 'anthropic' or 'openai' to use a real LLM; if unset, FixFlow runs offline with no API key. | |
| ANTHROPIC_API_KEY | No | Anthropic API key used when FIXFLOW_PROVIDER=anthropic, e.g. sk-... | |
| FIXFLOW_CONFIDENCE_THRESHOLD | No | Confidence threshold below which the agent escalates rather than guesses. | 0.35 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
FixFlow is an IT-support toolkit for laptops. Use triage_request for a full automated decision, or the individual tools to search the manuals, check a device warranty or open a ticket. Never close safety issues yourself: swelling, smoke or burning smells must use escalate.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| triage_requestB | Run the full FixFlow workflow on a support request: classify it, find the fix, check warranty, then answer it, open a ticket, or escalate it to a person. Returns the decision and the reasons. |
| search_manualsA | Search the laptop troubleshooting knowledge base. Returns the best-matching sections with article IDs. |
| check_warrantyA | Look up a device by serial number: model, plan and whether it is still under warranty. |
| create_ticketC | Open a support ticket. category must be one of the FixFlow categories; it decides the team. |
| get_ticketB | Get the status and details of a ticket by its ID (for example FF-1A2B3C4D). |
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 5 tools
triage_request is an orchestrator that internally performs classification, manual search, warranty lookup, ticket creation, and escalation, so it overlaps heavily with search_manuals, check_warranty, and create_ticket. The descriptions do signal 'full workflow' vs. individual step, which helps, but agents must decide between one-shot triage and composing primitives with no guidance on when to prefer which.
All five tools follow a clean verb_noun snake_case pattern: triage_request, search_manuals, check_warranty, create_ticket, get_ticket. Verbs are distinct and predictable, and the resource noun is always at the end.
Five tools is well-scoped for a support triage workflow: one orchestrator plus four focused primitives. Each tool earns its place and nothing feels padded or missing at the count level.
Ticket handling is incomplete: you can create and get a ticket but not update, close, comment on, or list tickets, so agents hit dead ends after creation. Similarly, search_manuals returns article IDs but there is no tool to fetch a full article, and escalation only exists implicitly inside triage_request.