Skip to main content
Glama
Sign In
yinxiang-mcp

yinxiang-mcp

by ArchChuan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

replace-super-note-block

Replace a specific block within a super note by providing the note GUID, block ID, and new block content. Requires confirmation to proceed.

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": {
      "guid": "<guid>",
      "blockId": "<blockId>",
      "block": "<block>",
      "confirm": "<confirm>"
    },
    "name": "replace-super-note-block"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidYes
blockYes
blockIdYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits. There is no mention of whether the operation is destructive, requires confirmation, or any side effects, despite the 'confirm' parameter hinting at a need for caution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While short, the description is under-informative. It does not earn its place as it provides no useful information for an AI agent to understand the tool's purpose or usage.

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

Completeness1/5

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

Given the complexity of four parameters (including a nested object) and the absence of an output schema, the description is woefully incomplete. It fails to explain what the tool does, how to use it, or what to expect as a result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to the parameters (guid, block, blockId, confirm). The 'block' parameter of type object is left completely unexplained, and no parameter constraints or formats are mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '替换块' (replace block) essentially restates the tool name without adding specificity. It does not clarify what kind of block is replaced or in what context, making it a tautology.

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

Usage Guidelines1/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 sibling tools like delete-super-note-block, append-super-note-blocks, or update-super-note. The description is silent on selection criteria or prerequisites.

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