Skip to main content
Glama
Sign In
witness

witness

by wookat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_errors

Retrieve console errors, page errors and HTTP failures with status 400 or higher to diagnose issues during evidence recording.

Instructions

All console errors, page errors and HTTP responses >= 400

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it usefully defines what counts as an error by including console errors, page errors, and HTTP >= 400 responses. However, it omits ordering, freshness, pagination or limits, and whether results are scoped to the current page or entire session, so important behavioral context is missing.

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 definition is a single compact phrase with no wasted wording and the returned-data categories are front-loaded. It could be slightly stronger as a complete sentence, but its brevity is appropriate for a zero-parameter retrieval tool.

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?

For a zero-parameter tool with no output schema, the description identifies the categories of returned data but does not describe the return shape, ordering, or scope. It is minimally viable but leaves real gaps that an agent would need to discover by invoking the tool.

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?

The tool has zero parameters, so there are no parameter semantics to document and the baseline is 4. The description does not need to compensate for any schema gaps.

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 the exact resource returned: console errors, page errors, and HTTP responses with status >= 400. It is clear enough to distinguish this from siblings like get_dom_state or get_body, but it is a noun phrase rather than an explicit verb+resource statement and does not explicitly differentiate itself from adjacent diagnostic tools.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling to prefer for related diagnostic data. An agent must infer the usage context entirely from the name and returned-data phrase.

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

Deploy Server

Other Tools