Gravitas-Core-MCP

by ahmed-coding

Overview Schema Source Related Servers Discussions Admin

Python

Local

browser_get_console_errors

Retrieve JavaScript console errors captured since the last page navigation. Helps identify client-side issues.

Instructions

Return collected JS console errors since last navigate.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses the behavioral trait of collecting errors since the last navigate, implying a reset on navigation. Without annotations, this carries the burden of transparency; it effectively communicates that this is a read operation with no destructive side effects.

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?

The description is a single, concise sentence that conveys the tool's purpose without any unnecessary words or details, earning its place efficiently.

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

Completeness4/5

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

For a tool with no parameters and a simple output (collected JS console errors), the description is adequate. It does not detail the return format or error types, but this is acceptable given the tool's low complexity and lack of output schema.

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

Parameters4/5

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

With zero parameters and schema description coverage at 100%, the baseline is 4. The description does not need to add parameter specifics as there are none, and it accurately reflects the tool's simplicity.

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 tool returns collected JS console errors since the last navigate, with a specific verb ('Return') and resource ('JS console errors'), and it distinguishes from sibling browser tools like browser_hover and browser_screenshot by focusing on console errors.

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 description implicitly indicates usage after a navigation by specifying 'since last navigate.' It provides clear context but does not explicitly mention when not to use it or alternatives, though the tool's purpose is straightforward with no parameters.

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