Skip to main content
Glama
KnobeDev

knobe-mcp-server

by KnobeDev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Seal multiple files as KNOBE documents

knobe_seal_batch

Seal multiple files as KNOBE documents in one batch. Confirm author once or per file; failed files won't stop the process.

Instructions

Seal a list of files (e.g. an entire conversion run) as KNOBE documents. The author is confirmed with the user ONCE for the whole batch by default; set confirm_each=true to prompt per file.

Files are processed independently: one failure does not stop the batch. The result lists sealed and failed files separately.

Args:

  • paths (string[]): files to seal (1-200).

  • confirm_each (boolean): prompt the user per file instead of once per batch. Default: false.

  • shared metadata fields as in knobe_seal_file (applied to every file; title always derives from each filename).

Returns: text summary plus structured {sealed: [...], failed: [{path, error}], author, aborted}. 'aborted' is true when the user declined an author prompt mid-batch; files already sealed before the decline are listed in 'sealed' and remain on disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags sealed into the payload.
pathsYesFiles to seal.
authorNoProposed author (person or organization) for the sealed attribution. The user is asked to confirm or change it before sealing unless KNOBE_NO_CONFIRM is set.
licenseNoLicense string sealed into the payload. Default: 'CC BY 4.0'.
summaryNoOne-paragraph summary sealed into the payload.
languageNoBCP-47 language tag of the body, e.g. 'en'.
overwriteNoReplace the output file if it already exists. Default: false.
confirm_eachNoAsk the user to confirm the author for every file instead of once per batch.
content_typeNoKNOBE content_type (e.g. 'original', 'adaptation', 'summary'). Default: 'original'.
contributionNoWhat the author contributed. Default: 'author'.
privacy_levelNoKNOBE privacy_level (e.g. 'public', 'internal'). Default: 'public'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorYes
failedYes
sealedYes
abortedYes

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Beyond annotations (which are minimal), the description fully discloses batch behavior: independent file processing, failure handling, return structure with sealed/failed/author/aborted, and that files remain on disk on abort. No contradictions with annotations.

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?

The description is well-organized with two paragraphs and bullet-point args. It is concise enough while covering key behaviors. Minor redundancy exists (e.g., explaining confirm_each twice), but overall efficient.

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?

Given 11 parameters, complete schema coverage, and an output schema, the description provides rich context: batch processing, error accumulation, abort handling, and links to sibling tools (knobe_seal_file). No gaps in explaining the tool's behavior or output.

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 baseline is 3. The description adds value by clarifying that metadata fields are applied per file, that title derives from filename, and provides detail on confirm_each and paths limits (1-200). This enriches understanding beyond schema alone.

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 clearly states 'Seal multiple files as KNOBE documents', using a specific verb and resource. It distinguishes from sibling tools like knobe_seal_file (single file) and knobe_seal_text (text input), making the batch scope explicit.

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?

The description explains when to use the tool (e.g., 'an entire conversion run') and describes the confirm_each behavior for per-file vs batch prompting. It references knobe_seal_file for shared metadata, providing implicit guidance on alternatives, though it lacks explicit 'when not to use' statements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KnobeDev/knobe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server