Skip to main content
Glama
MongLong0214

CommitLore

by MongLong0214
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

commitlore_verify_capture

Verifies a capture draft by checking evidence citations for verbatim matches against the transcript and diff, discarding fabricated quotes, and storing the verified result for staging.

Instructions

Verify a capture draft against the transcript and diff that were hashed at prepare time. Evidence citations are checked mechanically (verbatim match); fabricated quotes are discarded. Stores the verified result in the pending transaction for stage to consume.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diffNooptional: the staged diff, if you have it. Omit it and the server reads the staged diff itself and checks it against the hash prepare stored — the same guarantee, without asking you to reproduce content the server produced.
draftYesThe agent's draft, as the harvest contract specifies it: a JSON object with a "records" array. A bare JSON array of records is also accepted.
nonceYesthe 32-character lowercase hex nonce returned by prepare_capture
transcriptYesthe session transcript (same content hashed at prepare time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / properties / diff / description
      Previous value: -"the staged diff (same content hashed at prepare time)"New value: +"optional: the staged diff, if you have it. Omit it and the server reads the staged diff itself and checks it against the hash prepare stored — the same guarantee, without asking you to reproduce content the server produced."
    • changedInput schema / required
      Previous value: -[
-  "nonce",
-  "draft",
-  "transcript",
-  "diff"
-]New value: +[
+  "nonce",
+  "draft",
+  "transcript"
+]
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that it stores the verified result in a pending transaction and that evidence citations are mechanically checked, with fabricated quotes discarded. This adds meaningful behavioral context about the mutation and verification logic.

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?

Three sentences with no redundancy. The purpose is front-loaded, and each sentence delivers distinct information: the core verification action, the citation-checking behavior, and the storage outcome.

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?

The description does not specify the return value or what happens if verification fails, which is important given there is no output schema. It mentions the workflow (prepare, stage) but leaves response format and error handling unspecified.

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

Parameters4/5

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

While the schema already covers 100% of parameters, the description adds extra nuance: it explains the diff parameter can be omitted for the server to read the staged diff itself, and it clarifies the draft format (JSON object with a 'records' array, bare array accepted). This supplements the schema descriptions meaningfully.

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 description states a specific verb ('verify') and resource ('capture draft'), and clarifies the context by referencing 'hashed at prepare time' and 'for stage to consume'. This makes the tool's role in the workflow unambiguous and distinguishes it from the sibling prepare and stage tools.

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 in the prepare→verify→stage workflow but does not explicitly state when to use this tool over alternatives or when not to use it. There is no exclusions or alternative routing, so the guidance is only implicit.

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