Argus

Overview Schema Source Related Servers Discussions Admin

Verify State after Reload

verify_persistence

Destructive

Checks whether expected text appears or disappears after a fresh page load, helping detect fake deletes and failed edits. Review mismatches and recheck persistence failures without repeating writes.

Instructions

Fresh-load after_url and check target_text present/absent. Review mismatches; use suggested_verify with record_bug to recheck a persistence failure without repeating writes. clear_storage requires authority. Absence on login/error pages is inconclusive unless expect_status names the expected status.

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": {
      "expect": "<expect>",
      "target_text": "<target_text>"
    },
    "name": "verify_persistence"
  }
}

Input Schema

Name	Required	Description	Default
`expect`	Yes
`after_url`	No
`target_text`	Yes
`clear_storage`	No
`expect_status`	No

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.

Changed1 schema field changedv0.11.0Oct 27, 2026
- addedInput schema / properties / expect_status
```
Added value: +{
+  "default": 0,
+  "type": "integer"
+}
```
Changed5 schema fields changedv0.10.0Oct 26, 2026
- removedInput schema / properties / after_url / title
```
Removed value: -"After Url"
```
- removedInput schema / properties / clear_storage / title
```
Removed value: -"Clear Storage"
```
- removedInput schema / properties / expect / title
```
Removed value: -"Expect"
```
- removedInput schema / properties / target_text / title
```
Removed value: -"Target Text"
```
- removedInput schema / title
```
Removed value: -"verify_persistenceArguments"
```
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: -"verify_persistenceOutput"New value: +"AgentResult"

Addedv0.5.1Jul 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already flag destructive, non-idempotent, open-world behavior, and the description adds important context: fresh-loading, authority requirements for `clear_storage`, and when absence results are inconclusive. It does not fully explain what `clear_storage` destroys, but it does not contradict the 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?

The description is dense and front-loads the core action, with no obvious filler. It is somewhat telegraphic and could structure the caveats more clearly, but it remains efficient.

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 and annotations cover the safety profile, so return values need not be explained. However, for a destructive open-world verification tool with five parameters, the missing semantics for required `expect` and the underspecified `after_url` default leave the definition only partially complete.

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

Parameters2/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 parameter meaning. It mentions `after_url`, `target_text`, `clear_storage`, and `expect_status`, but it never explains the required `expect` parameter or its allowed values, leaving a critical call-time gap.

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

Purpose4/5

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

The description states a specific action: fresh-load `after_url` and check `target_text` present/absent. That clearly identifies a persistence-verification tool, though it does not explicitly contrast with nearby verification siblings such as `regression_check`.

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?

It gives useful usage context: review mismatches, use `suggested_verify` with `record_bug` to recheck persistence failures without repeating writes, and treat absence on login/error pages as inconclusive unless `expect_status` is supplied. It lacks a fully explicit when-to-use/when-not-to-use routing rule against alternative verification tools.

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