Skip to main content
Glama

flipper_kb_list

Read-onlyIdempotent

List saved task-knowledge notes to reuse prior work at the start of a task, then read a relevant note with the read tool instead of starting from scratch.

Instructions

List saved task-knowledge notes (the repo's memory of past tasks). Each note is a topic the agent learned; read one with flipper_kb_read. Check this at the start of a task to reuse prior work instead of starting from scratch.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds useful framing about what each entry represents ("a topic the agent learned") and that listing is a starting point rather than full retrieval. It does not say whether the listing is complete or capped, which is the main remaining unknown.

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?

Three short sentences, front-loaded with what the tool is, then how to act on a result, then when to call it. No filler and nothing repeated from the schema or annotations.

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

Completeness5/5

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

For a zero-parameter list tool with full annotation coverage and an output schema, nothing an agent needs in order to call it correctly is missing. The description covers identity, next step, and timing, and the return shape is handled by the output schema.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The description correctly avoids inventing filtering options that the schema does not support.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List saved task-knowledge notes") and immediately defines the concept as "the repo's memory of past tasks." It also distinguishes itself from flipper_kb_read by explicitly assigning the read-one-note behavior to that tool.

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?

Gives clear when-to-use guidance: "Check this at the start of a task to reuse prior work instead of starting from scratch." It also points to flipper_kb_read as the follow-up action. It does not mention when to prefer flipper_kb_search instead, though that name is not cited in the description.

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