Argus

Overview Schema Source Related Servers Discussions Admin

Navigate Browser

navigate

Destructive

Loads a URL within the authorized scope and returns the page observation, enabling the QA agent to inspect and verify web app behavior.

Instructions

Navigate to a URL within the authorized scope and return the observation.

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": {
      "url": "<url>"
    },
    "name": "navigate"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

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.

Changed2 schema fields changedv0.10.0Oct 26, 2026
- removedInput schema / properties / url / title
```
Removed value: -"Url"
```
- removedInput schema / title
```
Removed value: -"navigateArguments"
```
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"
```
Addedv0.5.2Oct 26, 2026
Removedv0.5.1Jul 21, 2026
First observedv0.4.0Apr 27, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent behavior, so the safety profile is covered structurally. The description adds the authorized-scope constraint and return behavior, but does not explain why navigation is destructive (loss of current page state) or how out-of-scope failures manifest, leaving real behavioral gaps.

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 no filler; the verb, scope constraint, and return behavior arrive in order of importance.

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?

An output schema exists, so not explaining the returned observation is acceptable. However, for an open-world, destructive, non-idempotent tool, the definition omits how it relates to session lifecycle (start_session/end_session) and what navigation destroys at the page level, so it is only minimally 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?

The single url parameter has 0% schema description coverage, so the description must compensate. It only restates 'a URL' with no format guidance (absolute vs relative, allowed schemes, whether it must be within the same origin), adding nothing the schema doesn't already show.

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 uses a clear verb+resource (navigate to a URL) and adds the scope constraint and that an observation is returned. It stops short of distinguishing itself from the go_back and start_session siblings, so the agent must infer the boundary between navigating to a URL and stepping back through history.

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

Usage Guidelines3/5

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

'Within the authorized scope' implies a permission boundary but never says when to choose this over go_back or start_session, nor what to do if the URL is outside scope. Usage is only implied, never stated as a when/when-not rule.

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