Skip to main content
Glama
KnobeDev

knobe-mcp-server

by KnobeDev

Seal a file as a KNOBE document

knobe_seal_file

Seal a text or markdown file into a KNOBE Protocol v1 document with cryptographic integrity and human-confirmed authorship.

Instructions

Seal an existing text/markdown file (e.g. the output of a document conversion) into a KNOBE Protocol v1 document with a cryptographic payload and body hash.

Before sealing, the user is asked (via elicitation) to confirm or change the author — pass 'author' as the proposal. If the client cannot elicit, 'author' or the KNOBE_DEFAULT_AUTHOR env var is required.

Args:

  • path (string): file whose content becomes the sealed body.

  • output_path (string, optional): where to write the sealed document. Default: source path with a .knobe.md suffix.

  • title (string, optional): sealed title. Default: source filename without extension.

  • author, summary, content_type, license, privacy_level, language, tags, contribution, overwrite: see field descriptions.

Returns: text summary plus structured {output_path, title, author, payload_hash, state, conformance}.

Errors:

  • "declined by the user" — the user rejected the author prompt; do not retry unprompted.

  • "already exists" — pass overwrite=true or a different output_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the source file to seal.
tagsNoTags sealed into the payload.
titleNoTitle sealed into the payload. Default: filename.
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.
output_pathNoDestination for the sealed .knobe.md. Default: derived from path.
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
stateYes
titleYes
authorYes
conformanceYes
output_pathYes
payload_hashYes
Behavior4/5

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

The description discloses key behaviors: user confirmation for author, defaults, and error cases. Annotations provide no hints, so the description carries the burden adequately. It could mention filesystem write behavior more explicitly.

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?

The description is well-organized with a clear overview, parameter summary, return type, and error list. Every sentence adds value, and it is front-loaded with the core purpose.

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?

Given the tool's complexity (12 parameters, elicitation, errors), the description covers the essential workflow and edge cases. The output schema exists, so return details are sufficient. Sibling comparisons are not needed for completeness.

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%, providing a baseline of 3. The description adds value by explaining the author elicitation, default derivations, and error handling, going beyond the schema field descriptions.

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 the verb 'seal' and the resource 'existing text/markdown file', and specifies the output as a KNOBE Protocol v1 document. It distinguishes from siblings like knobe_seal_text by targeting file input.

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 the author elicitation process, required conditions, and error handling. It does not explicitly contrast with sibling tools, but the context is clear and actionable.

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