Uxia

Get Insight

get_insight

Read-onlyIdempotent

Read a finding by exact ref from list_insights, including evidence quotes, impact and fix suggestions with recommendations, acceptance criteria and coding-agent prompts when available. Paywalled details may be redacted. Includes up to three available screenshot previews of referenced frames. Use get_frame_details for additional frames. Images may be unavailable. Use IDs from list_test_blocks to target a block/run; omission uses the documented defaults. Legacy tests also supported.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	Yes
`runId`	No
`testId`	Yes
`blockId`	No	Select one block from list_test_blocks. Omit to infer a sole relevant block; list_insights defaults to all AI blocks. Omit for legacy tests.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	No
`data`	No
`retry`	No
`runId`	No
`scope`	No
`title`	No
`frames`	No
`status`	No
`testId`	No
`blockId`	No
`message`	No
`paywall`	No
`category`	No
`nextStep`	No
`priority`	No
`relevance`	No
`userImpact`	No
`description`	No
`severityCard`	No
`totalTesters`	No
`fixSuggestion`	No
`reporterCount`	No
`businessImpact`	No
`testerEvidence`	No
`primaryCategory`	No
`secondaryCategory`	No
`technicalComplexity`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedOutput schema / properties / data / properties / reporterCount
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / reporterCount
```
Added value: +{
+  "type": "integer"
+}
```
Changed43 schema fields changedSep 30, 2026
- removedOutput schema / properties / data / properties / businessImpact / $ref
```
Removed value: -"#/properties/businessImpact"
```
- addedOutput schema / properties / data / properties / businessImpact / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / category / $ref
```
Removed value: -"#/properties/category"
```
- addedOutput schema / properties / data / properties / category / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / description / $ref
```
Removed value: -"#/properties/description"
```
- addedOutput schema / properties / data / properties / description / type
```
Added value: +"string"
```
- removedOutput schema / properties / data / properties / fixSuggestion / $ref
```
Removed value: -"#/properties/fixSuggestion"
```
- addedOutput schema / properties / data / properties / fixSuggestion / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "acceptanceCriteria": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "explanation": {
+        "type": "string"
+      },
+      "prompt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "explanation",
+      "acceptanceCriteria",
+      "prompt"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / data / properties / frames / $ref
```
Removed value: -"#/properties/frames"
```
- addedOutput schema / properties / data / properties / frames / items
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / data / properties / frames / type
```
Added value: +"array"
```
- removedOutput schema / properties / data / properties / paywall / $ref
```
Removed value: -"#/properties/paywall"
```
- addedOutput schema / properties / data / properties / paywall / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / data / properties / paywall / properties
```
Added value: +{
+  "feature": {
+    "type": "string"
+  },
+  "hiddenCount": {
+    "type": "integer"
+  }
+}
```
- addedOutput schema / properties / data / properties / paywall / required
```
Added value: +[
+  "hiddenCount",
+  "feature"
+]
```
- addedOutput schema / properties / data / properties / paywall / type
```
Added value: +"object"
```
- removedOutput schema / properties / data / properties / primaryCategory / $ref
```
Removed value: -"#/properties/primaryCategory"
```
- addedOutput schema / properties / data / properties / primaryCategory / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / priority / $ref
```
Removed value: -"#/properties/priority"
```
- addedOutput schema / properties / data / properties / priority / type
```
Added value: +"string"
```
- removedOutput schema / properties / data / properties / ref / $ref
```
Removed value: -"#/properties/ref"
```
- addedOutput schema / properties / data / properties / ref / type
```
Added value: +"string"
```
- removedOutput schema / properties / data / properties / relevance / $ref
```
Removed value: -"#/properties/relevance"
```
- addedOutput schema / properties / data / properties / relevance / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / secondaryCategory / $ref
```
Removed value: -"#/properties/secondaryCategory"
```
- addedOutput schema / properties / data / properties / secondaryCategory / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / severityCard / $ref
```
Removed value: -"#/properties/severityCard"
```
- addedOutput schema / properties / data / properties / severityCard / enum
```
Added value: +[
+  "High",
+  "Medium",
+  "Low"
+]
```
- addedOutput schema / properties / data / properties / severityCard / type
```
Added value: +"string"
```
- removedOutput schema / properties / data / properties / technicalComplexity / $ref
```
Removed value: -"#/properties/technicalComplexity"
```
- addedOutput schema / properties / data / properties / technicalComplexity / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / testerEvidence / $ref
```
Removed value: -"#/properties/testerEvidence"
```
- addedOutput schema / properties / data / properties / testerEvidence / items
```
Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "gender": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hasMisclickEvidence": {
+      "type": "boolean"
+    },
+    "misclickContext": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "quote": {
+      "type": "string"
+    },
+    "testerName": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "testerName",
+    "quote",
+    "hasMisclickEvidence",
+    "misclickContext",
+    "gender"
+  ],
+  "type": "object"
+}
```
- addedOutput schema / properties / data / properties / testerEvidence / type
```
Added value: +"array"
```
- removedOutput schema / properties / data / properties / title / $ref
```
Removed value: -"#/properties/title"
```
- addedOutput schema / properties / data / properties / title / type
```
Added value: +"string"
```
- removedOutput schema / properties / data / properties / totalTesters / $ref
```
Removed value: -"#/properties/totalTesters"
```
- addedOutput schema / properties / data / properties / totalTesters / type
```
Added value: +"integer"
```
- removedOutput schema / properties / data / properties / userImpact / $ref
```
Removed value: -"#/properties/userImpact"
```
- addedOutput schema / properties / data / properties / userImpact / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / retry / properties / arguments / $ref
```
Removed value: -"#/properties/nextStep/properties/arguments"
```
- addedOutput schema / properties / retry / properties / arguments / additionalProperties
```
Added value: +{}
```
- addedOutput schema / properties / retry / properties / arguments / type
```
Added value: +"object"
```
First observedSep 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful behavior beyond that: paywalled details may be redacted, only up to three screenshot previews are returned, and images may be unavailable. It still doesn't say what happens on an invalid or expired ref.

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?

Front-loaded with what the tool returns, then caveats, then parameter sourcing. Dense but every sentence carries information; only the trailing 'Legacy tests also supported' is thinly connected to the rest.

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

Completeness4/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-value detail is not strictly required, yet the description usefully previews the payload (quotes, impact, fix suggestions, prompts). Remaining gaps are minor: no failure/redaction-trigger detail and no explicit runId/testId semantics.

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 only 25%, so the description must carry weight. It clarifies that ref comes from list_insights and that blockId comes from list_test_blocks with omission using documented defaults, but it never explains the distinction between runId and testId or the 24-hex format constraint.

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 and resource ('Read a finding by exact ref from list_insights') and immediately enumerates exactly what the finding contains. An agent can distinguish it from list_insights (listing) and show_evidence (evidence display) without opening either 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 concrete routing guidance: use 'get_frame_details for additional frames' and take block/run IDs 'from list_test_blocks'. It does not explicitly say when to prefer this over show_evidence or list_insights, so it falls short of full when/when-not coverage.

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

All Uxia 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?