Navvi

Overview Schema Source Related Servers Discussions Admin

navvi_atomic

List all available atomic browser tools with parameters for quick reference. Call to get a summary of tools and workflow.

Instructions

Quick reference for atomic browser tools (navvi_click, navvi_find, navvi_fill, etc.).

Atomic tools are always available. Call this for a summary of tools and workflow.

Example: navvi_atomic() → lists all atomic tools with parameters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "navvi_atomic"
  }
}

Input Schema

Name	Required	Description	Default
`enable`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.21.0May 26, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It declares the tool is a reference (lists tools) and implies non-destructive, read-only behavior. Sufficient for a meta-tool.

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?

Two concise sentences plus an example. Front-loaded with purpose. No waste; each part contributes meaning.

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 description adequately explains the tool's role as a reference. The presence of an output schema covers return values, but the missing parameter description creates a gap, making it slightly incomplete.

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 input schema has one boolean parameter 'enable' with zero description coverage. The description does not mention it, leaving its purpose unclear. Agents may not know what 'enable' does.

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?

The description clearly states it is a 'quick reference' that lists atomic browser tools, distinguishing it from sibling tools like navvi_click, navvi_find, etc., which are the actual action tools.

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 says 'Call this for a summary of tools and workflow,' providing clear usage context. However, no explicit exclusions or when-not-to-use guidance, though not critical for a reference tool.

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