Skip to main content
Glama
Sign In
SiYuan MCP Server

SiYuan MCP Server

by xgq18237
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

batch_set_database_cells

Set multiple database cells in SiYuan by providing the database ID and an array of cell updates with values.

Instructions

批量设置数据库单元格；values 使用思源批量 AV Value 结构

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>",
      "values": "<values>"
    },
    "name": "batch_set_database_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
avIDYes思源块、文档、笔记本或数据库 ID
valuesYes单元格更新对象

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations do not provide much (all false), and the description only says 'batch set database cells'. It does not disclose any side effects, auth needs, or behavior beyond the obvious mutation. No mention of what happens on failure or partial updates.

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 extremely concise with two clauses, front-loaded with the primary action. No unnecessary words. Every character earns its place.

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?

Given the simplicity (2 parameters, fully described in schema) and no output schema, the description is minimally adequate. It provides the batch intent and a format hint, but lacks context on constraints (e.g., all cells same database), error handling, or atomicity.

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% with descriptions for both parameters. The description adds the important format hint 'values 使用思源批量 AV Value 结构', which clarifies the structure of the values array, adding value beyond the schema's 'cell update object'.

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 clearly states '批量设置数据库单元格' (batch set database cells), indicating a batch operation. It distinguishes from the sibling tool 'set_database_cell' (singular). However, the mention of '思源批量 AV Value 结构' may be unclear to non-Chinese users.

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 on when to use this tool versus alternatives. The sibling 'set_database_cell' implies this is for batch updates, but no conditions or exclusions are stated.

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