Skip to main content
Glama
InDate
by InDate

console

Retrieve, filter, and clear browser console messages for debugging web applications.

Instructions

Monitor and manage console messages. Actions: list, get, recent, search, clear, setObjectDepth

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoMessage ID (required for get)
fullNoReturn full message without smart truncation (default: false)
typeNoMessage type filter (log, error, warn, etc.)
countNoNumber of recent messages (default: 50)
depthNoObject expansion depth 1-10 (default: 2)
flagsNoRegex flags (default: "")
limitNoMax messages to return (default: 100 for list, 50 for search/recent)
actionYesConsole action: list, get, recent, search, clear, setObjectDepth
offsetNoMessages to skip (for list action, default: 0)
reasonNoWhy console needs clearing (required for clear)
patternNoRegex pattern (required for search)
argsIndexNoSpecific args array index to return
textLimitNoMax characters to return from text
textOffsetNoCharacter offset for text extraction
connectionReasonYesConnection reference (e.g., "unnamed-connection-default" or your renamed tab)
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It mentions actions like 'clear' but does not disclose that it is destructive or requires a reason (as indicated by the schema). No details on idempotency, side effects, or read-only actions are provided.

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 extremely concise (two sentences) with no filler. It front-loads the purpose and lists actions, making it quick to parse. Every word serves a purpose.

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

Completeness2/5

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

Given the tool's complexity (15 parameters, multiple actions, no output schema), the description is insufficient. It does not explain how each action behaves, when to use specific parameters, or what the return format looks like, leaving the agent underinformed.

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

Parameters3/5

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

The schema covers 100% of parameters with descriptions, so baseline is 3. The description adds no additional parameter guidance beyond listing actions, which is already in the schema's 'action' enum.

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 clearly states that the tool is for monitoring and managing console messages, and lists the specific actions available. This distinguishes it from sibling tools like 'network' or 'content', though it could be more explicit about the scope (e.g., browser console).

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?

No guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or exclusions. The description only states what the tool does, not when or why an agent would choose it over others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/InDate/cdp-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server