Skip to main content
Glama
Sign In
bwiki-mcp

bwiki-mcp

by putaojuju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bwiki_type

Type text into a targeted input field on BWIKI pages. Use a CSS selector to specify the field, with an option to clear existing content before entering new text.

Instructions

在输入框中输入文本。

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>",
      "text": "<text>"
    },
    "name": "bwiki_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes要输入的文本
clearNo是否先清空输入框
selectorYesCSS选择器

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not mention whether the optional 'clear' flag is used, whether typing simulates real keystrokes, if input events are triggered, or what happens after typing. This is a notable gap for a mutating action.

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, short sentence with no wasted words. It is front-loaded with the primary action, though it could have included more detail without becoming verbose.

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?

The description is too incomplete for the tool's complexity. It omits behavior around the 'clear' parameter, return values (the tool has no output schema), and usage context. An agent would be under-informed about side effects and prerequisites.

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 input schema fully documents all three parameters (selector, text, clear) with descriptions, so the schema already provides the necessary parameter semantics. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 states the core action clearly: 'Enter text in the input box.' It distinguishes from sibling actions like bwiki_click or bwiki_navigate by specifying the typing action, though it does not explicitly mention the selector parameter that targets the input element.

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 any prerequisites like ensuring the element is visible or waiting for it. The description is purely declarative with no contextual instructions.

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