Skip to main content
Glama
Sign In
vault-engine

vault-engine

by Bagas10k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vault_scaffold_note

Generate standards-compliant Markdown note templates with kebab-case filenames, complete YAML frontmatter, test invariants, and closing lines for Otak-Koding vaults.

Instructions

[NOTE SCAFFOLDER] Hasilkan templat catatan Markdown baru yang 100% mematuhi standar vault Otak-Koding: Nama berkas otomatis kebab-case, frontmatter YAML lengkap 6 kunci wajib, template invarian uji, dan baris penutup.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "judul": "<judul>"
    },
    "name": "vault_scaffold_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
judulYes
skippedNoImplementasi lanjutan yang belum mendesak.
add_whenNoKetika kebutuhan sistem di lingkungan produksi telah terbukti secara empiris.
kategoriNobackend
tags_jsonNo
isi_singkatNoUraian arsitektur teknis dan doktrin sistem.
tautan_jsonNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the generated artifact's structure: automatic kebab-case filename, six mandatory YAML frontmatter keys, test-invariant template, and closing line. However, it does not state whether the tool writes to disk, whether it overwrites existing files, or what permissions are required.

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 a single compact sentence with the core action front-loaded. The bracketed '[NOTE SCAFFOLDER]' tag is slightly noisy, and the dense Indonesian phrasing could be clearer, but the content is efficient.

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

Completeness2/5

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

For a creation tool with seven parameters, no annotations, and no schema descriptions, the definition is under-specified. It describes the output template but leaves parameter roles, file-writing side effects, and overwrite behavior undocumented; the output schema helps with return values but not input semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are seven input parameters with 0% schema description coverage, so the description must compensate. It adds no meaning for any parameter, including required 'judul' and optional fields such as 'kategori', 'tags_json', and 'tautan_json'.

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?

The description uses a specific verb and resource: 'Hasilkan templat catatan Markdown baru' (generate a new Markdown note template). It further scopes the purpose with vault-standard compliance details, making it clearly distinct from the read-oriented siblings such as vault_search and vault_lint_note, though it does not explicitly name those siblings.

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

Usage Guidelines2/5

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

The description explains what the tool generates but gives no guidance on when to use it versus alternatives like vault_lint_note or vault_search. It also omits prerequisites, such as whether a note must already exist or whether this is intended only for new notes.

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