Skip to main content
Glama
Sign In
SiYuan MCP Server

SiYuan MCP Server

by xgq18237
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

remove_database_rows

Destructive

Delete specific database rows in SiYuan Note by providing the database attribute view ID and array of item IDs.

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": {
      "avID": "<avID>",
      "itemIDs": "<itemIDs>"
    },
    "name": "remove_database_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
avIDYes思源块、文档、笔记本或数据库 ID
itemIDsYes条目 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

The description simply states 'delete', which aligns with the destructiveHint=true annotation, but it adds no additional behavioral context such as whether the operation is reversible, requires permissions, or affects other data. Since the annotation already covers destructiveness, the description provides minimal extra value.

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 unnecessary words. It is appropriately concise, though it could be more informative 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?

Given the large number of sibling tools with similar deletion purposes, the description fails to provide enough context for an agent to distinguish this tool from others. The missing guidance on when to use this tool specifically (versus delete_block, remove_doc, etc.) makes it incomplete for the decision-making process.

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%, with both parameters having descriptions in the schema. The tool description does not add any new information beyond what the schema already provides, so it meets the baseline but does not exceed it.

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 '删除数据库条目' (delete database entries) clearly states the verb (delete) and resource (database entries). However, it does not differentiate this tool from sibling tools like delete_block, remove_doc, or remove_database_column, which also perform deletions on various resources.

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. There is no mention of prerequisites, context, or what makes this tool distinct from other deletion tools (e.g., delete_block vs. remove_database_rows).

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