Skip to main content
Glama
Sign In
bwiki-mcp

bwiki-mcp

by putaojuju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bwiki_add_category

Insert category tags into BWIKI pages at the correct position, avoiding duplicate entries.

Instructions

为BWIKI页面添加分类标记。智能插入到正确位置，避免重复。

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": {
      "pageName": "<pageName>",
      "category": "<category>"
    },
    "name": "bwiki_add_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryNo编辑摘要
categoryYes分类名称，如 '游戏UI组件'
pageNameYes页面名称

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations are absent, so the description carries the transparency burden. It adds useful behavioral details: '智能插入到正确位置' (intelligently inserts into the correct position) and '避免重复' (avoids duplicates). However, it does not disclose edit effects, permission requirements, or behavior when the category already exists beyond duplicate avoidance.

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 one concise sentence that front-loads the primary action and adds two valuable behavioral clauses. Every phrase earns its place with no unnecessary words.

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?

For a simple 3-parameter tool with full schema coverage, the description is largely complete: it states the purpose and key behavior (smart placement, duplicate avoidance). It lacks when-to-use guidance, but this is minor given the low complexity and rich schema.

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?

Schema description coverage is 100%, so baseline 3 applies. The description does not add extra parameter semantics beyond what the schema already provides for pageName, category, and summary.

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 action (add a category marker) and the target (BWIKI page), using a specific verb and resource. It distinguishes from sibling tools such as bwiki_edit_page and bwiki_get_categories, as no other sibling covers category addition.

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 explicit guidance is given about when to use this tool versus alternatives like bwiki_edit_page. The description implies usage for adding categories but lacks exclusions or alternative recommendations.

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