Skip to main content
Glama
Sign In
ragnarok

ragnarok

by freyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search

Find relevant vault notes by combining meaning and keyword matching, returning each note with its best section and optional filters for vault, project, area, and type.

Instructions

Hybrid search (meaning and keywords) over the vault notes. Returns notes, each with its best section.

    Filters: vault (the name of a vault folder), project (folder slug), area, type (research,
    spec, plan, summary, drivers, guide, note, ...). include_private works only when the user allows it.

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

Input Schema

NameRequiredDescriptionDefault
areaNo
typeNo
limitNo
queryYes
vaultNo
projectNo
include_privateNo
include_archivedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "searchDictOutput",
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return shape and one genuinely useful constraint ('include_private works only when the user allows it'), but it omits ranking order, how the 'best section' is chosen, whether results are truncated, and any read-only/safety statement.

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?

Two short, front-loaded parts: the core behavior first, then a filter inventory. Little waste, though the filter list reads as a spec dump and the trailing whitespace/line breaks add noise.

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 needn't be spelled out. But for an 8-parameter, annotation-free search tool, leaving limit and include_archived (default true) undocumented, plus no ranking or pagination note, leaves real gaps.

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% with 8 parameters, so the description must compensate. It explains vault ('the name of a vault folder'), project ('folder slug'), area, and type (with an enum-ish list of examples), but says nothing about query, limit, or include_archived — the last being a meaningful non-obvious default of true.

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?

The description states a specific mechanism and resource: 'Hybrid search (meaning and keywords) over the vault notes,' plus the return shape ('notes, each with its best section'). That distinguishes it reasonably well from the find_*/list_* siblings, which target specific entities, but it never explicitly contrasts itself with them.

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 rather than stated: the hybrid semantic+keyword framing signals this is the discovery tool for vault content. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for a narrower lookup, so an agent must infer the routing.

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

Deploy Server

Other Tools