Asklear Browser MCP

Official

by Asklear

Overview Schema Source Related Servers Discussions Admin

Python

Local

fill

Populate a form input field in the local Chrome browser via the Asklear extension. Page data remains on your machine.

Instructions

Run the local Chrome browser fill operation. Page results stay local to the Agent.

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": {
      "session_id": "<session_id>",
      "snapshot_id": "<snapshot_id>",
      "element_ref": "<element_ref>",
      "value": "<value>"
    },
    "name": "fill"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`request_id`	No
`session_id`	Yes
`element_ref`	Yes
`snapshot_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

D1.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry all behavioral disclosure. The only hint is 'Page results stay local to the Agent,' which is vague and could be interpreted in multiple ways (e.g., no server submission, local state only?). It fails to disclose common aspects like whether the fill triggers events, overwrites existing values, or requires focus.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences) but not effective. The first sentence is redundant with the tool name, and the second adds little actionable information. It is under-specified rather than efficiently written.

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

Completeness1/5

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

Given 5 parameters, no schema descriptions, no output schema, and no annotations, the description is severely incomplete. It omits return values, error conditions, side effects, and any usage context, making it impossible to invoke correctly without additional external knowledge.

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?

With schema description coverage at 0%, the description must clarify meaning for parameters like element_ref, snapshot_id, and value. The description does not mention any parameters or how they relate to the operation. This is a critical gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Run the local Chrome browser fill operation,' which largely restates the tool name ('fill'). It does not clearly specify that this tool populates a form field or input element with a given value. The phrase 'Page results stay local to the Agent' hints at some scope behavior but does not clarify the core purpose.

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

Usage Guidelines1/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 versus sibling tools like click, navigate, or extract. No prerequisites, when-to-use, or alternatives are mentioned, leaving the agent without context for appropriate invocation.

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

Deploy Server