Skip to main content
Glama

flipper_kb_search

Read-onlyIdempotent

Search task-knowledge notes for a term and return matching notes with line references, so you can start a task by finding what was already learned.

Instructions

Search all task-knowledge notes for a term; returns matching notes+lines. Run at the START of a task to find what was already learned about 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": "flipper_kb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile needs no restating. The description adds little beyond the output schema: it notes the search covers "all" notes and returns notes+lines, but says nothing about matching semantics, result limits, or pagination. Not contradictory, just thin on behavior beyond structured fields.

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 sentences, front-loaded with the action and scope, then the usage cue. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be spelled out, and the tool is a simple one-parameter search. Purpose and timing are covered; the only meaningful gap is query matching semantics, which is minor for a KB lookup.

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 0% for the single `query` parameter, so the description carries the burden. It conveys that the parameter is a search "term" against note text, which is real added meaning, but it leaves open whether matching is substring, whole-word, case-sensitive, or multi-term.

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 uses a specific verb and resource ("Search all task-knowledge notes for a term") and states the return shape ("matching notes+lines"), so the agent knows exactly what operation this is. It does not explicitly name a sibling such as flipper_kb_list or flipper_kb_read to contrast scope, which keeps it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete timing cue — "Run at the START of a task to find what was already learned about it" — which is a real usage condition, not just an implied one. There are no exclusions or named alternatives (e.g., when to list instead of search), so it falls short of the 5 bar.

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