Skip to main content
Glama
u9401066

asset-aware-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

citation_bundle

Export verified citation bundles with exact quotes, locators, and context. Generate Foam-compatible evidence packs and update index notes.

Instructions

Export citation-ready evidence spans as a verified bundle.

Each entry carries AssetRef, exact quote/hash, locator metadata, context, conservative CRAAP scaffold, optional verification status, and Foam anchor metadata. Use output_format="foam" for a Foam-compatible evidence pack. Pass wiki_root to write the pack and optionally update an index note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
doc_idYes
span_idNo
overwriteNo
wiki_rootNo
index_pathNo
span_kindsNo
output_pathNo
citation_keyNo
update_indexNo
output_formatNomarkdown
citation_contractNo
citation_metadataNo
include_verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • addedInput schema / properties / citation_contract
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Citation Contract"
+}
    • addedInput schema / properties / citation_metadata
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Citation Metadata"
+}
  2. First observedv0.7.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the bundle contents, the Foam output option, and the side effect of writing a pack and optionally updating an index note. However, it does not disclose overwrite behavior, whether verification is always applied, or other potential mutations beyond the wiki_root path.

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 dense but not bloated; each sentence conveys useful information about contents, format, or side effects. It is front-loaded with the main purpose. Minor structural friction comes from burying the parameter tips mid-description.

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 15-parameter tool with no output schema and no annotations, this description is incomplete. It explains the high-level deliverable and a couple of options, but an agent cannot confidently determine how to set query, span kinds, citation metadata, overwrite, output paths, or how the return value will be structured.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It adds meaning for only a few parameters: output_format, wiki_root, and update_index. The remaining 12 parameters—including doc_id, span_id, span_kinds, citation_contract, citation_metadata, include_verification, and output_path—remain essentially undocumented.

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 opens with a specific verb-plus-resource statement: 'Export citation-ready evidence spans as a verified bundle,' which clearly conveys the tool's core function. It details what each entry contains, but it does not explicitly differentiate this tool from siblings like find_evidence_spans or verify_citation_ref.

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 gives parameter-level guidance ('Use output_format="foam"', 'Pass wiki_root'), but does not state when to choose this tool over alternatives or when not to use it. No exclusions, prerequisites, or sibling comparisons are provided, leaving tool-selection guidance to inference.

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