Skip to main content
Glama
flukeatzerocool

Infobroker

by flukeatzerocool
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Knowledge Base

infobroker_manage_kb
Destructive

Search, ingest, list, or delete entries in a local knowledge base while managing at-rest encryption. Archive reports and revisit stored content without external fetches.

Instructions

Manage the local knowledge base: search cached content, ingest text or URLs, list/get/delete entries, view stats, and manage at-rest encryption. Use when you need to archive a generated report (ingest with source_type 'report' and save_to 'kb'), revisit stored content, or manage encryption keys. Do NOT use for fresh external search (use infobroker_search_web) or to fetch a new page (use infobroker_fetch_page). The delete action is destructive and cannot be undone; a lost encryption key makes the store unrecoverable by design. Parameter semantics: action selects the operation; query for search, text/url plus title and collection for ingest, source_url for get/delete, and operation with key_file for the encryption sub-actions; source_type and freshness_tier tag an ingest and filter search/list; save_to defaults to 'kb', format to 'markdown', max_results to 8; last_updated is auto-detected from fetched URLs when omitted. Responses carry an [OK] or [ERROR] envelope: search/list/get return entries, stats returns counts, delete reports the chunks removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to fetch and index (for ingest action)
textNoRaw text to index (for ingest action)
queryNoSearch query (for search action)
titleNoDocument/report title
actionYesOperation to perform
formatNoFile format for disk savemarkdown
save_toNoWhere to save (ingest action): kb, disk, or both. Default kb
key_fileNoPath to a key file (generate_key writes here; rekey reads the target key from here). Never pass the secret itself — only a file path.
operationNoSub-operation for the 'encryption' action
collectionNoCollection name
source_urlNoSource URL filter (get/delete action) or identity for ingest
max_resultsNoMaximum results to return (1-50, default 8)
source_typeNoSource type (tag on ingest; filter on search/list)
last_updatedNoSource last-updated date to store (e.g. '2026-08-24'); auto-detected from fetched URLs when omitted
freshness_tierNoFreshness tier tag on ingest (e.g. 'report', 'evergreen')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the specifics annotations cannot: delete is irreversible, and a lost encryption key makes the store unrecoverable by design. It also discloses the [OK]/[ERROR] response envelope. It stops short of covering auth/permission requirements or any concurrency behavior, so a 4 rather than a 5.

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?

Front-loaded with purpose, then usage, then the destructive warning, then parameter mapping — a sensible priority order with almost no filler. The closing parameter sentence is dense and list-like, slightly harder to parse than the rest, but every clause carries information.

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 15-parameter, 7-action tool with no output schema, the description covers action routing, destructive risk, and return shape ([OK]/[ERROR], entries for search/list/get, counts for stats, chunks removed for delete). An agent has everything needed to select and invoke it without opening the 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real cross-field semantics the schema cannot express: which parameters apply to which value of `action`, the source_type/freshness_tier tag-vs-filter duality, and that last_updated is auto-detected from fetched URLs. It does restate a few defaults already present in the schema (save_to, format, max_results), which keeps it out of the top band.

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?

The description names the resource (local knowledge base) and enumerates the concrete operations (search, ingest, list/get/delete, stats, encryption), so the agent knows exactly what the tool covers. It explicitly distinguishes itself from siblings by naming infobroker_search_web and infobroker_fetch_page as the tools for fresh external work.

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

Usage Guidelines5/5

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

Gives positive triggers (archive a generated report with source_type 'report' and save_to 'kb', revisit stored content, manage encryption keys) and explicit exclusions with the alternative tool named for each. This is the when/when-not/alternatives pattern at full strength.

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