Skip to main content
Glama
Sign In
Kilonova MCP

Kilonova MCP

by MilnaOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kb_backup

Mirror the knowledge base folder to OneDrive and preview the copy with a dry run before files are transferred. This backup step keeps project context synchronized and avoids accidental overwrites.

Instructions

Mirror the KB folder to OneDrive. Use dry=true to preview without copying.

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

Input Schema

NameRequiredDescriptionDefault
dryNoPreview only — no copying
kb_onlyNoKB folder only (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden for a write/mutation operation. It never says whether the mirror overwrites or deletes extra files at the destination, whether OneDrive authentication must already be configured, whether it is incremental or full, or what a success response looks like.

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, zero waste, with the core action front-loaded and the safe-preview hint immediately after. Nothing could be removed without losing information.

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

Completeness3/5

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

Low-complexity tool with a fully documented two-parameter schema, so the essentials are covered. But with no annotations and no output schema, the description should also cover destination/overwrite semantics and auth prerequisites for a copy operation, and it does not.

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 description coverage is 100%, so both parameters (dry, kb_only) are already documented in the schema. The description restates dry=true's meaning but adds nothing about kb_only or about the default behavior when flags are omitted, so the baseline 3 applies.

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?

States a specific verb and resource: "Mirror the KB folder to OneDrive." The operation is unmistakably different from the sibling tools (kb_search, kb_load, kb_write, kb_topics), though the description never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

Gives one concrete usage hint — set dry=true to preview without copying — which tells the agent how to safely explore before committing. It stops short of saying when this tool should be chosen, whether it is idempotent/safe to re-run, or what to do if OneDrive is already populated.

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