Skip to main content
Glama
Sign In
pony-browser-mcp

pony-browser-mcp

by pssrh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_set_date

Set any date input reliably, including native fields, masked text boxes, and calendar pickers, by attempting value insertion and picker navigation with verification. Use when standard fill fails or a calendar widget opens.

Instructions

Robustly set a date input — handles native , masked text inputs (e.g. MM/DD/YYYY), and calendar pickers (MUI, react-datepicker, AntD, Lexical/Meta). Tries native value-set, format-aware typing via Input.insertText, and ARIA-based picker navigation in sequence with read-back verification. Use instead of browser_fill when fill fails or for any input that opens a calendar widget.

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": {
      "selector": "<selector>",
      "date": "<date>"
    },
    "name": "browser_set_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesISO date string (YYYY-MM-DD), e.g. "2026-05-15"
selectorYesCSS selector for the date input element
skip_pickerNoIf true, only try native + masked paths and skip calendar-picker navigation (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.8/5.0
Behavior5/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 discloses the fallback strategy in detail, including native value setting, format-aware typing via Input.insertText, ARIA-based picker navigation, and read-back verification. This is exceptional transparency for an unannotated tool.

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?

Two sentences, front-loaded with the core purpose and followed directly by usage guidance. No filler, no repetition of schema content, and every phrase adds information.

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?

The description covers what the tool does, when to use it, and the internal fallback/verification behavior, which is enough for an agent to invoke it correctly. However, with no output schema, it does not explicitly describe return values or failure behavior, so a small gap remains.

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 input schema already provides 100% description coverage for all parameters, so the baseline is 3. The description adds value by explaining the strategy sequence, which clarifies what skip_picker=true actually avoids and how the date parameter is applied across different input types.

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's purpose: robustly set a date input, covering native, masked, and calendar-picker variants. It explicitly names browser_fill as an alternative, which distinguishes it from sibling tools without needing to inspect schemas.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Use instead of browser_fill when fill fails or for any input that opens a calendar widget.' This gives the agent a clear decision rule and names the alternative tool.

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