Skip to main content
Glama
Sign In
bwiki-mcp

bwiki-mcp

by putaojuju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bwiki_evaluate

Execute custom JavaScript on BWIKI pages to handle advanced operations, including direct CodeMirror manipulation.

Instructions

在BWIKI页面上执行JavaScript代码。用于高级操作如直接操作CodeMirror。

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": {
      "code": "<code>"
    },
    "name": "bwiki_evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes要执行的JavaScript代码

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states that it executes JavaScript, but fails to mention potential side effects, page state modifications, or that arbitrary code could cause navigation or data changes. Given the power of this tool, the lack of these disclosures is a significant gap.

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?

The description is two sentences long and directly states purpose and a use case. Every word earns its place with no redundancy or filler.

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

Completeness3/5

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

For a code execution tool with no output schema and no annotations, the description is adequate for selection but sparse on invocation details. It does not explain return values, error handling, or safety considerations. The example helps, but a more comprehensive description would improve completeness for such a powerful tool.

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 schema already describes the only parameter ('code' as JavaScript code to execute), achieving 100% coverage. The description adds the usage context of operating on BWIKI and mentions CodeMirror, but does not add new parameter-level detail beyond the schema, so it stays at the baseline.

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: 'Execute JavaScript code on the BWIKI page.' It uses a specific verb ('execute') and identifies the resource (JavaScript on the page), distinguishing it from sibling tools like bwiki_navigate and bwiki_click by being the only one that deals with script execution.

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

Usage Guidelines4/5

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

The description provides context for when to use the tool: 'Used for advanced operations such as directly manipulating CodeMirror.' This gives a concrete use case and implies it is for tasks beyond standard interactions, though it does not explicitly list alternatives or exclusions.

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