mcp-workspace

Search notes

notes_search

Read-only

Search Markdown notes for case-insensitive text matches and return up to 20 line results with file paths and line numbers; files over 100000 bytes are skipped and counted.

Instructions

Find lines that contain a text (case-insensitive) in the Markdown notes. Returns up to 20 matches with path and line number; notes larger than 100000 bytes are skipped and counted.

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": {
      "query": "<query>"
    },
    "name": "notes_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`matches`	Yes
`skippedFiles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/ non-destructive/closed-world, so the bar is lower, yet the description adds real operational context: case-insensitive matching, a result cap, and the fact that notes over 100000 bytes are skipped and counted. It doesn't say how matches are ordered or what the 'counted' skip tally looks like in the response.

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 dense sentences, front-loaded with the core behavior and followed by the return/limitation facts. No wasted language; every clause conveys actionable information.

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

Completeness4/5

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

An output schema exists, so return-value explanation is not required, and the description still adds the important skip/count edge case. It is nearly complete for a 2-parameter read tool, with the only gap being the unexplained limit parameter 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 description coverage is 0%, so the description must carry parameter meaning. It explains the query semantics (case-insensitive substring, min/max length aside) but says nothing about the limit parameter — its default of 10, its 1-20 range, or how it interacts with the stated cap of 20 matches, which is slightly misleading given the default.

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?

States a specific verb and resource: find lines containing text in Markdown notes, with matching mode (case-insensitive). It is clearly distinct from notes_list and notes_read by virtue of being a content search rather than enumeration or full read, though no sibling is named explicitly.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'Find lines that contain a text' rather than stated as when-to-use guidance. There is no explicit statement about when to prefer notes_read or notes_list over this search, and no prerequisites or exclusions beyond the size-skip note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server