Skip to main content
Glama

obsidian_search_notes

Search an Obsidian vault by text, tag, or thematic area to locate relevant notes and narrow results with filters.

Instructions

Recherche ciblée et filtrée à travers les notes du coffre Obsidian de Noa

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

Input Schema

NameRequiredDescriptionDefault
tagNoTag sans le dièse (ex: 'projet', 'golang', 'vuejs')
poleNoPôle thématique spécifique pour restreindre la recherche
limitNoNombre maximum de résultats
queryNoTerme textuel à rechercher dans le titre, tags ou contenu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet "recherche" only weakly implies a non-destructive read. It says nothing about result ordering, whether full note content or snippets are returned, or how the default limit of 10 behaves — all of which matter for planning a search call.

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 tight sentence with no filler, though its brevity is also the source of the missing usage and behavioral detail. It is front-loaded with the verb and resource, which is good structure.

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

Completeness2/5

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

For a 4-parameter search tool with no annotations and no output schema, the description omits result format, ranking behavior, and how query interacts with tag and pôle filters. The schema covers the parameters, but an agent still lacks what it needs to interpret results.

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 100%, so tag, pôle, limit and query are already well documented in the schema, establishing a baseline of 3. The description's "ciblée et filtrée" loosely gestures at the filters but adds no semantics beyond what the schema states.

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 ("Recherche") and resource ("notes du coffre Obsidian de Noa"), with an adjective pair ("ciblée et filtrée") distinguishing it from a plain note read. It does not name the sibling it replaces, so differentiation from obsidian_read_note or obsidian_get_moc is left to inference.

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 explicit when-to-use or when-not-to-use guidance; the only hint is the word "filtrée", which implies this is the tool for narrowed queries but never says so or names an alternative. An agent must infer its place relative to read_note and get_moc.

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