Skip to main content
Glama

Provenance Stamp

provenance_stamp

Creates a .provenance.json sidecar for artifacts, recording sha256 checksum, file metadata, source, toolchain, git details, author, tags, and notes offline.

Instructions

Writes a .provenance.json sidecar next to a saved artifact (tox, recipe note, recipe bundle, component bundle). Records the sha256 checksum, file size, mtime, source COMP path, originating tdmcp tool, toolchain versions, best-effort git metadata, author, tags, and freeform notes. Offline — no TD bridge required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFree-form tags for vault search.
extraNoTool-specific extras, e.g. {nodes:7, connections:9}.
notesNoShort human note to attach to the sidecar.
authorNoAuthor label. Defaults to TDMCP_AUTHOR env var then os.userInfo().username.
sourceNoWhere/what produced this artifact.
overwriteNoReplace an existing sidecar. Set false to refuse if one exists.
include_gitNoCapture git commit/branch/dirty from the artifact's directory (best-effort).
artifact_kindNoWhat kind of artifact this is — hint only, not validated.other
artifact_pathYesAbsolute or vault-resolved path to the file to stamp.
Behavior3/5

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

Annotations already indicate non-read-only and non-destructive behavior. Description adds that it works offline and includes best-effort git metadata. However, it does not disclose failure modes, permissions, or prerequisites (e.g., artifact must exist).

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 concise sentences: first states the action and artifact, second enumerates recorded contents. Front-loaded, no redundancy, every sentence earns its place.

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?

Given the tool has no output schema, the description adequately explains what is written. However, it does not cover error conditions, required artifact existence, or what happens if the artifact path is invalid. For a 9-parameter write tool, more context on preconditions would improve completeness.

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 baseline is 3. Description lists many recorded fields (sha256, size, author, tags, etc.) that align with schema properties, but does not add new meaning beyond the schema descriptions. Marginal added value.

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?

Description clearly states the tool writes a .provenance.json sidecar next to an artifact, listing specific recorded fields (sha256, size, mtime, source, etc.). Verb 'Writes' and resource 'sidecar' are specific, and the tool is distinct from siblings like checksum_and_verify_pack or version_library_asset.

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?

The description implies usage (when provenance metadata is needed) and notes offline capability, but does not explicitly state when to use this tool over alternatives or provide exclusions. No sibling differentiation is mentioned.

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/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server