Skip to main content
Glama
mcp-notes-server

mcp-notes-server

Search notes

search_notes
Read-only

Finds notes by searching keywords across titles, tags, and body content, returning the best matches with their full text so you can locate stored information quickly.

Instructions

Keyword search across note titles, tags and bodies. Returns the best matches with full content.

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": "search_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 5)
queryYesSpace-separated keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the searched fields (titles, tags, bodies), relevance ranking ('best matches'), and that full content is returned rather than snippets — all of which shape how an agent should use results.

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 tight sentences with zero filler: the search scope is front-loaded and the return behavior follows. Nothing redundant and nothing that could be cut.

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?

For a simple two-parameter read tool with no output schema, the description covers what is searched and what comes back ('full content'), which is the key missing piece an agent would otherwise lack. Minor gaps remain around result ordering and empty-result behavior, but nothing essential is absent.

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%, so both 'query' and 'limit' are fully documented in the schema, including the default of 5 and max of 20. The description reinforces keyword-style querying but adds no syntax or formatting detail the schema doesn't already supply, so the baseline 3 applies.

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 ('keyword search across note titles, tags and bodies') and what it returns, which clearly separates it from get_note (single record by ID) and list_notes (unfiltered enumeration). It does not explicitly name a sibling as an alternative, keeping it just below a 5.

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?

The description implies the tool is for keyword-based lookup ('Keyword search... space-separated keywords'), which lets an agent infer it should be used when it has search terms rather than an ID. However, there is no explicit statement of when to prefer search_notes over list_notes or get_note, and no mention of result limits or exclusions.

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