Skip to main content
Glama
owrede

vault-memory

by owrede
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

assemble_dossier

Read-onlyIdempotent

Resolve a type/key pair to an anchor document and walk its backlinks into a structured dossier with citation packets and property rollups.

Instructions

Resolve a {type, key} pair to an anchor document and walk its backlinks into a structured dossier: { anchor (citation packet), linked_documents (citation packets + relation), property_rollups (linked_count, linked_types, status_distribution) }. Strict properties.type match (D-03). The key matches the candidate's title OR any entry in properties.aliases (D-04). v2.0.0 returns relation:"wikilink" on every linked_documents entry (the v1 wikilinks table is the only edge source); Phase 4 (GRA-04) widens to typed edges. Superseded backlinks are NOT filtered — dossiers show the whole picture (CONTEXT D-04).

Input Schema

NameRequiredDescriptionDefault
keyYesCandidate key — matches the document's title OR any entry in properties.aliases (D-04)
typeYesExact-match value for properties.type on the anchor document (D-03 — no fuzzy match)
vaultsNoRestrict to these vault names; defaults to all configured
max_charsNoGlobal UTF-16 body character budget. Sections defaults to 6000; zero excludes body text. Metadata is always body-free.
projectionNoOptional v2 projection; sections requires heading_paths. Defaults to the legacy response.
heading_pathsNoExact heading paths on the anchor, or filters on section-search results.
include_observationsNoInclude explicitly categorized statements when the derived source hash is fresh; preserves provenance and shares the body budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.5.0
    • addedInput schema / properties / heading_paths
      Added value: +{
+  "description": "Exact heading paths on the anchor, or filters on section-search results.",
+  "items": {
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / include_observations
      Added value: +{
+  "description": "Include explicitly categorized statements when the derived source hash is fresh; preserves provenance and shares the body budget.",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_chars
      Added value: +{
+  "description": "Global UTF-16 body character budget. Sections defaults to 6000; zero excludes body text. Metadata is always body-free.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / projection
      Added value: +{
+  "description": "Optional v2 projection; sections requires heading_paths. Defaults to the legacy response.",
+  "enum": [
+    "full",
+    "metadata",
+    "sections"
+  ],
+  "type": "string"
+}
  2. First observedv2.0.0-rc.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/no-destruction, but the description adds real behavioral context: strict properties.type matching (no fuzzy match), key matching against title or aliases, the guarantee that relation is always "wikilink" in v2.0.0, the Phase 4 widening plan, and the notable decision that superseded backlinks are NOT filtered. That last point is exactly the kind of non-obvious behavior an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, which is good, but the prose is dense with internal ticket references (D-03, D-04, GRA-04, CONTEXT D-04) that convey little to an invoking agent, and the embedded output-shape enumeration could be tighter. It is informative but not economically written.

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?

With no output schema, the description appropriately fills that gap by enumerating anchor, linked_documents, and property_rollups fields. Combined with the behavioral caveats (unfiltered superseded backlinks, single edge source), an agent has enough to call and interpret it, though projection/heading_paths interplay is only lightly touched.

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% and all six optional params carry their own descriptions, so the schema does the heavy lifting. The description restates the type/key semantics and outlines the property_rollups shape but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 first sentence states a precise verb+resource: resolve {type, key} to an anchor document, walk backlinks, and build a dossier with named output sections. This clearly separates it from siblings like list_backlinks or get_document_bundle, which do not synthesize a structured multi-section dossier.

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?

Usage is only implied through the resolution/backlink-walking mechanics. It never says when to prefer this over list_backlinks, get_document_bundle, or expand, nor when a dossier is the wrong tool. The strict-match and alias rules hint at input expectations but do not guide tool selection.

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