fixragent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIXRAGENT_API_KEY | Yes | The API key for fixragent.com. Sent as the x-triage-key header. | |
| FIXRAGENT_API_URL | No | Optional base URL for the fixragent API. Defaults to https://fixragent.com. | https://fixragent.com |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| try_sampleA | Returns a stored fixRAgent assessment of a sample photo from fixRAgent's test set (an HVAC air handler and furnace), labelled SAMPLE, plus how to get a free key. Needs no key and no input, reads no photo and spends nothing. The result is a sample, not an assessment of anyone's own photo. |
| assess_property_photoA | Assesses a photo of something in a building — an appliance, a boiler, a pipe, a water heater, an electrical panel, a fitting, a leak, damage — and reports what it is, how urgent it is and which trade it needs. Returns the fixed contract: what the asset is, whether a fault is visible, one of four urgency words (EMERGENCY, TODAY, THIS WEEK, WHENEVER), which trade to call, a line to say to the resident, and how many independent reads agreed. One call reads the photo on fixragent.com and spends one request from the key's daily allowance. Sent with NO key, it reads the real photo up to 3 times per connection in a rolling 24 hours (a small free allowance, shared across every keyless caller up to a daily ceiling); past either limit it returns fixRAgent's stored sample result, labelled SAMPLE, and says how to get a free key with no such limit. Scope: photos of building assets and faults. It does not assess people, pets, injuries, rashes, medical or veterinary questions, vehicles, food, documents, screenshots or photos of screens. It is not an emergency service: a fire, a gas smell or hissing gas, a carbon-monoxide alarm sounding, water pouring onto live electrics or anyone hurt needs the local emergency number (911 in the US), not a photo assessment. It does not price repairs, book contractors or decide insurance claims; it routes the job, it does not quote or dispatch it. |
| get_triage_profileA | Returns a saved fixRAgent assessment by its diagnosis_id (from an assessment, or the last part of a fixragent.com/c/ link). Read only: it never re-reads the photo, never calls the model and spends nothing from the daily allowance. It takes one id and returns one assessment with no contact details of any kind, the same assessment anyone with its fixragent.com/c/ link can open. It needs no key; if a key is sent, it must be a valid one. Reads are limited to 20 an hour per address, shared with assessments. |
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
The three tools have clearly distinct purposes: assess_property_photo reads a new photo, try_sample returns a fixed stored sample, and get_triage_profile retrieves an existing assessment by id. Descriptions explicitly separate them, including the keyless/sample behavior of assess_property_photo versus try_sample, so an agent can tell them apart without confusion.
All names use a consistent snake_case verb_noun pattern (assess_property_photo, try_sample, get_triage_profile). The verb choices (assess, try, get) are appropriate and predictable, with no mixed casing or stylistic drift.
Three tools is slightly lean but well matched to a focused photo-triage service: assess, sample, and retrieve. Nothing feels redundant or missing at the count level, though the surface is minimal.
The core lifecycle is covered: create an assessment, retrieve it by id, and a no-key sample path. Gaps are minor and largely by design (no listing/search of past assessments, no delete), and the service explicitly declines pricing, dispatch, and emergency handling, so these are intentional scope limits rather than failures.