Skip to main content
Glama
Sign In
SiYuan MCP Server

SiYuan MCP Server

by xgq18237
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_database_cell

Sets a single cell value in a SiYuan database attribute view using the AV Value JSON structure.

Instructions

设置单个数据库单元格；value 使用思源 AV Value JSON 结构

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>",
      "keyID": "<keyID>",
      "itemID": "<itemID>",
      "value": "<value>"
    },
    "name": "set_database_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
avIDYes思源块、文档、笔记本或数据库 ID
keyIDYes思源块、文档、笔记本或数据库 ID
valueYesAV Value 对象
itemIDYes思源块、文档、笔记本或数据库 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations lack behavioral hints (all false). Description only says 'set' but does not disclose side effects, permissions, or what happens if cell doesn't exist.

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?

Single sentence, front-loaded with action and resource. Appropriate length for a simple tool, though could include brief usage context.

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?

Description lacks explanation of how the IDs relate (database, column, row) and what happens after setting. No return value information. Not sufficient for agent to understand full behavior.

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 coverage is 100%, but description adds value by specifying the AV Value JSON structure for the 'value' parameter. Other parameters (avID, keyID, itemID) have no additional explanation beyond schema.

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?

Description clearly states action ('set single database cell') and resource ('database cell'), and mentions value format. Distinguishes from sibling 'batch_set_database_cells' by specifying 'single'.

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 on when to use this tool vs alternatives like batch_set_database_cells. No mention of prerequisites or when not to use.

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