Skip to main content
Glama
Sign In
cairn

cairn

by juw12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search

Read-onlyIdempotent

Search project memory in plain Markdown across ideas, tasks, decisions, notes and journal pages; every word must match, and matching titles and tags rank first.

Instructions

Search ideas, tasks, decisions, notes and journal pages. Every word must match; titles and tags rank first. Use it before answering 'why did we...' questions.

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
typeNoOnly this kind of note
limitNo
queryYesWords to find, #tags allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: AND-style matching semantics ('Every word must match') and a relevance order (titles and tags rank first), which tells the agent how to interpret and sequence results.

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?

Three compact sentences with the resource scope front-loaded, followed by matching behavior and then the use case. Nothing is redundant, though the final usage sentence is terse enough to feel compressed rather than fully elaborated.

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?

For a search tool with three parameters and no output schema, the description covers matching and ranking but says nothing about what a result contains, whether pagination beyond limit exists, or how empty results are signaled. Adequate to invoke correctly, but an agent still has gaps about the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and already documents the type enum, limit bounds, and #tag syntax. The description adds real meaning beyond that by explaining that query terms are conjunctive rather than OR-matched, and by implying ranking affects result order for the limit parameter.

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?

Names a specific verb (search) and the exact resource set (ideas, tasks, decisions, notes, journal pages), which separates it from retrieval siblings like read_note or recent. It stops short of naming a sibling alternative to disambiguate against, so it is clear but not fully differentiating.

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?

Gives one concrete usage context: call it before answering 'why did we...' questions. There is no when-not guidance and no mention of when list_notes, recent, or context would be preferred, leaving the agent to infer the boundary.

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