yinxiang-mcp

find-notes

Search notes using keywords and filter by notebook to retrieve note titles and metadata.

Instructions

搜索笔记。可按搜索词(words)和/或笔记本(notebookGuid)过滤,返回标题等元数据。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find-notes"
  }
}

Input Schema

Name	Required	Description
`words`	No	搜索词, 支持印象笔记搜索语法(可选)
`maxResults`	No	最大返回条数(1-50), 默认 10
`notebookGuid`	No	限定笔记本 guid(可选)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Lacks annotations; description says returns 'title and other metadata' but does not disclose pagination behavior, rate limits, or read-only status. Insufficient detail for a search tool.

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?

Two concise sentences, front-loaded with core purpose, no wasted words.

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?

Adequate for a simple search tool but missing details on return format, sorting, and error handling. No output schema to compensate.

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 covers all 3 parameters with descriptions (100% coverage); description adds that results include title and metadata but does not enhance parameter understanding beyond schema.

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?

Description clearly states the tool searches notes with optional filters, which is specific and distinct from siblings like 'get-note' but does not explicitly differentiate.

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 versus alternatives such as 'list-notebooks' or 'get-note'. Does not mention excluded cases 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