Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_tap_ledger

Return a tap’s ledger of discovered documents—URI, filename, status, hashes, and first/last-seen timestamps—so re-runs skip unchanged files. Clear one URI or all entries to force reprocessing or a full rescan.

Instructions

For a document tap: return the ledger of discovered documents (URI, filename, status, hashes, first/last seen timestamps). The ledger is what tells the platform which documents have already been processed so re-runs skip unchanged files. Pass 'clear_uri' to delete one entry (forces that document to be re-processed on the next run) or 'clear_all=true' to wipe the entire ledger (forces a full re-scan).

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": {
      "name": "<name>"
    },
    "name": "get_tap_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the document tap
clear_allNoOptional. If true, deletes the entire ledger for this tap, forcing every document to be re-processed on the next run.
clear_uriNoOptional. If set, deletes the ledger entry for this URI so the document is re-processed on the next run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does the important work: it discloses that a 'get_'-named tool also deletes ledger entries, and spells out the consequence of each deletion. It omits whether clears are reversible, whether they require elevated permissions, and whether the ledger is returned before or after the clear applies.

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?

Three sentences, front-loaded with what is returned and followed by the mutation semantics. The middle sentence explaining the ledger's role is slightly long but earns its place by motivating why clearing matters.

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?

There is no output schema, and the description compensates by listing the returned fields, plus it fully covers all three parameters and their effects. Missing are edge cases an agent might hit: behavior for an unknown tap name, size limits of the ledger, or what happens if both clear options are supplied.

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 the parameters are already documented. The description's wording for 'clear_uri' and 'clear_all' largely restates the schema text ('re-processed on the next run', 'deletes the entire ledger'), adding little beyond it; the enumerated return fields describe output rather than parameter meaning.

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?

Names a specific resource ('ledger of discovered documents') and enumerates what it contains (URI, filename, status, hashes, first/last seen timestamps), which lets an agent distinguish it from get_tap_logs or get_tap_state. It does not explicitly contrast itself with those siblings, so identification relies on the agent knowing what the others do.

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

Usage Guidelines4/5

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

Explains the retrieval use case (see which documents have been processed so re-runs skip unchanged files) and states exactly when to use each mutation parameter, including the downstream effect ('forces that document to be re-processed', 'forces a full re-scan'). It stops short of naming an alternative tool or any prerequisites/ordering constraints between the two clear options.

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