Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Fill input

fill

Set input, textarea, or contenteditable values in a single call that fires input and change events, targeting an element by ref, CSS selector, visible text, or role and name.

Instructions

Set an input/textarea/contenteditable value in one call (fires input + change). Target one of: ref (preferred), selector, text, or role+name.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot, e.g. e12. Preferred over selectors.
nameNoAccessible name to combine with role.
roleNoARIA role, e.g. button, link, textbox, checkbox, combobox.
textNoVisible text to match (first match wins).
exactNoRequire exact text/name match.
valueYesValue to set.
confirmNoConfirm a high-impact action when the server policy is ask.
observeNoReturn a compact change observation after the action (default true).
selectorNoCSS selector (use when no ref is available).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden, and it delivers the important detail that the tool fires both input and change events and works across input, textarea, and contenteditable elements. It omits what happens to pre-existing content and what occurs when no element matches the target, which matters for a mutating 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 tightly packed sentences with zero filler. The core action and its event side effects come first, followed by the targeting rule, so the most decision-relevant information is front-loaded.

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?

With nine parameters, no output schema, and minimal annotations, the description covers the essential behavior and the targeting model well. The remaining gaps are the confirm-policy pathway and no-match error behavior, which an agent would benefit from knowing before invoking a write action.

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?

Schema coverage is 100%, so baseline is 3, but the description adds a real semantic constraint the schema does not express: ref, selector, text, and role+name are mutually exclusive targeting modes with a stated priority. It does not mention `confirm` or `observe`, though the schema documents both adequately.

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 gives a concrete verb and a well-scoped resource: 'Set an input/textarea/contenteditable value in one call'. It also names the exact mutation semantics (fires input + change), which separates it from keystroke-level typing tools. It does not name a sibling such as `type`, so the contrast with that tool is left implicit.

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

Usage Guidelines3/5

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

There is explicit guidance on how to pick a target, including a stated preference ('ref (preferred)'), which is genuinely useful. However, that is parameter-selection guidance rather than tool-selection guidance: nothing says when to use `fill` instead of `type` or `select`, and no exclusion conditions are given.

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