Argus

Overview Schema Source Related Servers Discussions Admin

Record QA Observation

record_observation

Record qualitative visual, usability, content, responsive, or accessibility evidence separately from bugs to keep QA observations organized and actionable.

Instructions

Record qualitative visual, usability, content, responsive or accessibility evidence separately from bugs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "evidence": "<evidence>"
    },
    "name": "record_observation"
  }
}

Input Schema

Name	Required	Default
`title`	Yes
`category`	No	visual
`evidence`	Yes
`screenshot`	No	auto

Output Schema

Name	Required	Description	Default
`data`	No
`run_id`	Yes
`stages`	No
`status`	Yes
`recovery`	No
`operation`	Yes
`error_code`	Yes
`session_state`	Yes
`schema_version`	No
`progress_omitted`	No
`progress_delivery_failed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.10.0Oct 26, 2026
- removedInput schema / properties / category / title
```
Removed value: -"Category"
```
- removedInput schema / properties / evidence / title
```
Removed value: -"Evidence"
```
- removedInput schema / properties / screenshot / title
```
Removed value: -"Screenshot"
```
- removedInput schema / properties / title / title
```
Removed value: -"Title"
```
- removedInput schema / title
```
Removed value: -"record_observationArguments"
```
Changed12 schema fields changedOct 26, 2026
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / properties / error_code / title
```
Removed value: -"Error Code"
```
- removedOutput schema / properties / operation / title
```
Removed value: -"Operation"
```
- removedOutput schema / properties / progress_delivery_failed / title
```
Removed value: -"Progress Delivery Failed"
```
- removedOutput schema / properties / progress_omitted / title
```
Removed value: -"Progress Omitted"
```
- removedOutput schema / properties / recovery / title
```
Removed value: -"Recovery"
```
- removedOutput schema / properties / run_id / title
```
Removed value: -"Run Id"
```
- removedOutput schema / properties / schema_version / title
```
Removed value: -"Schema Version"
```
- removedOutput schema / properties / session_state / title
```
Removed value: -"Session State"
```
- removedOutput schema / properties / stages / title
```
Removed value: -"Stages"
```
- removedOutput schema / properties / status / title
```
Removed value: -"Status"
```
- removedOutput schema / title
```
Removed value: -"AgentResult"
```

Changed14 schema fields changedv0.5.2Oct 26, 2026

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": true,
+  "title": "Data",
+  "type": "object"
+}

addedOutput schema / properties / error_code

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Error Code"
+}

addedOutput schema / properties / operation

Added value: +{
+  "title": "Operation",
+  "type": "string"
+}

addedOutput schema / properties / progress_delivery_failed

Added value: +{
+  "default": false,
+  "title": "Progress Delivery Failed",
+  "type": "boolean"
+}

addedOutput schema / properties / progress_omitted

Added value: +{
+  "default": 0,
+  "title": "Progress Omitted",
+  "type": "integer"
+}

addedOutput schema / properties / recovery

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Recovery",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / run_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Run Id"
+}

addedOutput schema / properties / schema_version

Added value: +{
+  "const": 1,
+  "default": 1,
+  "title": "Schema Version",
+  "type": "integer"
+}

addedOutput schema / properties / session_state

Added value: +{
+  "title": "Session State",
+  "type": "string"
+}

addedOutput schema / properties / stages

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Stages",
+  "type": "array"
+}

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "completed",
+    "error"
+  ],
+  "title": "Status",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "operation",
+  "status",
+  "session_state",
+  "run_id",
+  "error_code"
+]

changedOutput schema / title

Previous value: -"record_observationOutput"New value: +"AgentResult"

Addedv0.5.1Jul 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds the useful fact that observations are stored in a separate stream from bugs, but says nothing about persistence, session requirements, or what the 'auto' screenshot behavior does.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the categories and the bug-vs-observation distinction are both packed in without redundancy.

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

Completeness3/5

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

The output schema exists, so return values need no explanation, but for a write tool with a 0%-covered 4-parameter schema the description leaves real gaps: the loose 'evidence' string format and the unexplained 'screenshot: auto' default. Adequate but thin for the schema richness.

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 description coverage is 0%, so the description must carry the load. It does partially compensate by naming valid category values (visual, usability, content, responsive, accessibility) that the schema never enumerates, but it says nothing about the format of 'evidence', what 'screenshot: auto' does, or defaults.

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 ('Record ... evidence') and enumerates the observation types (visual, usability, content, responsive, accessibility). Critically, it distinguishes itself from the sibling record_bug by declaring observations are recorded 'separately from bugs', so an agent can route 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?

The phrase 'separately from bugs' gives a clear selection rule versus record_bug, which is the closest alternative. It stops short of explicit exclusions or prerequisites (e.g., must a session be active?), so it is clear context rather than full routing guidance.

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