fixRAgent maintenance triage

Read back a saved triage profile

get_triage_profile

Read-onlyIdempotent

Returns a saved fixRAgent assessment by its diagnosis_id (from an assessment, the last part of a fixragent.com/c/ link, or the h- code that comes with a fixragent.com photo link once the photo has been added there; with no photo added yet, it reports that there is no result). 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`diagnosis_id`	Yes	The UUID of a saved assessment, the last path segment of a fixragent.com/c/<id> link, or h- followed by the code from a fixragent.com photo link.

Output Schema

TableJSON Schema

Name	Required	Description
`core`	No
`reason`	No
`agreement`	No
`config_id`	No
`share_url`	No
`created_at`	No
`handoff_id`	No	h-<code>: get_triage_profile reads the result back once the photo is added there.
`instruction`	No	What to do with a not-assessed reply, and that nothing in it is fixRAgent's.
`diagnosis_id`	No
`not_assessed`	No	true = nothing was assessed; there is no fixRAgent urgency, trade or finding. Pass add_photo_url on.
`problem_text`	No	On a not-assessed reply: the words the caller sent, handed back so a photo added in the card goes with them.
`add_photo_url`	No	fixragent.com page where the person adds the photo and sees the full Triage Profile.
`engine_version`	No
`rubric_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedOutput schema / properties / problem_text

Added value: +{
+  "description": "On a not-assessed reply: the words the caller sent, handed back so a photo added in the card goes with them.",
+  "type": "string"
+}

Changed6 schema fields changedOct 16, 2026

addedOutput schema / properties / add_photo_url

Added value: +{
+  "description": "fixragent.com page where the person adds the photo and sees the full Triage Profile.",
+  "type": "string"
+}

addedOutput schema / properties / handoff_id

Added value: +{
+  "description": "h-<code>: get_triage_profile reads the result back once the photo is added there.",
+  "type": "string"
+}

addedOutput schema / properties / instruction

Added value: +{
+  "description": "What to do with a not-assessed reply, and that nothing in it is fixRAgent's.",
+  "type": "string"
+}

addedOutput schema / properties / not_assessed

Added value: +{
+  "description": "true = nothing was assessed; there is no fixRAgent urgency, trade or finding. Pass add_photo_url on.",
+  "type": "boolean"
+}

addedOutput schema / properties / reason

Added value: +{
+  "enum": [
+    "no_photo",
+    "photo_not_arrived",
+    "not_added_yet"
+  ],
+  "type": "string"
+}

removedOutput schema / required

Removed value: -[
-  "diagnosis_id",
-  "share_url",
-  "core"
-]

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / diagnosis_id / description

Previous value: -"The UUID of a saved assessment, or the last path segment of a fixragent.com/c/<id> link."New value: +"The UUID of a saved assessment, the last path segment of a fixragent.com/c/<id> link, or h- followed by the code from a fixragent.com photo link."

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / diagnosis_id / description

Previous value: -"The UUID from assess_property_photo, or the last path segment of a fixragent.com/c/<id> link."New value: +"The UUID of a saved assessment, or the last path segment of a fixragent.com/c/<id> link."

First observedSep 27, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnly/idempotent annotations: no photo re-read, no model call, no spend from the daily allowance, no contact details in the response, no key required but a supplied key must be valid, and a 20/hour shared rate limit. That is exactly the operational context an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and every clause is substantive, but the single sprawling sentence with nested parentheticals is denser than needed and pushes the cost/privacy/rate-limit facts into a run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and the description still covers auth posture, cost, privacy, no-result behavior and rate limiting. Nothing required to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter's schema description already explains the UUID / link-segment / h- code forms. The description restates the same id sources without adding syntax or format meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Returns a saved fixRAgent assessment by its diagnosis_id'. It is the only read-back tool against siblings assess_property_photo (which creates an assessment) and try_sample, so an agent can place it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when it applies (an existing diagnosis_id from a link or photo code) and the no-result case when no photo has been added yet. It does not explicitly name a sibling as the alternative for producing a fresh assessment, so it stops short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fixRAgent maintenance triage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?