Gravitas-Core-MCP

by ahmed-coding

Overview Schema Source Related Servers Discussions Admin

Python

Local

browser_navigate

Navigate to a specified URL using Playwright. Control browser behavior by setting wait conditions.

Instructions

Navigate to URL (Playwright).

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": "browser_navigate"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`wait_until`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only mentions 'Playwright' but fails to explain key behaviors like whether it waits for full page load, handles redirects, or errors. The wait_until parameter in the schema hints at waiting, but the description is silent.

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

Conciseness2/5

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

While the description is short (4 words), it is under-specified. Conciseness should not come at the expense of necessary detail. There is no structure or front-loading of key information beyond the basic action.

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

Completeness1/5

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

Given low schema coverage, no output schema, and no annotations, the description must compensate. It fails to provide enough context for an AI agent to correctly invoke the tool, lacking details on behavior, parameter usage, and return values.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the JSON schema does not describe parameters. The description adds no meaning beyond the schema; it does not explain the 'url' format or valid values for 'wait_until'. The agent gets no clarity on how to use these parameters.

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 the verb 'Navigate' and the resource 'URL', which is a specific action. It distinguishes from sibling tools like browser_hover or browser_screenshot, as navigation is a distinct browser action.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or when not to use it (e.g., if page is already loaded).

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