mailnotmilk

by jrb00013

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

browser_extract_messages

Extract visible chat turns from the open browser AI page to make assistant conversations available to coding agents.

Instructions

Parse visible chat turns from the open browser AI page.

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_extract_messages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Jul 31, 2026

TDQS

C2.7/5.0

Behavior3/5

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

The description discloses that only visible chat turns are parsed and that it relies on the open browser page, which are useful behavioral constraints. However, it does not mention whether the tool is read-only, how it handles missing browser context, or the structure of returned data. With no annotations, more detail is needed to fully understand its behavior.

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 description is a single sentence and immediately states the action, making it concise and front-loaded. However, it is succinct to the point of omitting key operational details that would help the agent invoke the tool correctly.

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 lack of annotations and output schema, the description is too minimal. It does not explain the 'limit' parameter, the return format, or what constitutes 'visible' chat turns, leaving the agent to infer essential behavior. The tool is relatively simple, but the description does not cover its full context.

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?

The sole parameter 'limit' is not mentioned in the description, and the input schema provides only type and min/max, leaving its purpose ambiguous. The description fails to add any meaning to this parameter, making it unclear whether it controls message count, timeout, or something else.

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 the tool parses visible chat turns from the open browser AI page, using the specific verb 'Parse' and specifying both the resource (chat turns) and source (open browser page). It distinguishes itself from sibling chat/browser tools by focusing on extraction from the current page view, though it doesn't explicitly name alternatives.

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 like chat_history or browser_screenshot. The description implies a use case but offers no exclusions or prerequisite conditions, leaving the agent to infer appropriate usage.

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