Skip to main content
Glama

Search notes

search_notes
Read-onlyIdempotent

Search notes and bookmarks by keyword or tag to return relevance-ranked matches for quick context retrieval.

Instructions

Full-text search over notes and bookmarks, best matches first.

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
tagNoOnly search notes with this tag
limitNo
queryYesWords to look for in titles and bodies

Output Schema

NameRequiredDescriptionDefault
hitsYes
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds useful ranking semantics (results ordered by relevance) and scope (covers bookmarks as well as notes), but says nothing about result volume, the 50-item cap, or empty-result behavior beyond what the output schema and schema maximums already convey.

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?

A single front-loaded sentence with zero filler; the resource and result ordering come first. It is arguably terse to the point of leaving search semantics unexplained, but nothing is redundant.

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?

An output schema exists so return values need not be described, and annotations cover safety. Still, for a search tool with a tag filter, the description omits how filtering interacts with matching and whether search is fuzzy or exact — gaps an agent would need to call it confidently.

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 67%, with query and tag documented in the schema while limit has no description. The description adds no meaning beyond the schema — it doesn't clarify how tag combines with the query (AND vs. narrowing) or what limit does to ranking. Baseline 3 is appropriate for mid-range coverage.

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 ("Full-text search over notes and bookmarks") plus a ranking behavior ("best matches first"), so the operation is unambiguous. It does not name a sibling to distinguish itself from, e.g. list_notes or get_note, leaving that differentiation implicit.

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 phrase "full-text search" implies it should be used when the agent has keywords rather than a known identifier, which weakly contrasts with get_note/list_notes. However, no explicit when-to-use, when-not-to-use, or named alternative is given.

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