Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_tap_state

Retrieve a tap's incremental-sync bookmark or cursor saved after its last successful run to see where it will resume or debug re-fetching and skipped windows.

Instructions

Get a tap's incremental-sync state — the bookmark/cursor its script saved after the last successful run (injected into the next run as the DATRIS_TAP_STATE env var). Returns {tap, state, updatedAt, updatedBy}; state is null when the tap has never committed state (non-incremental tap, or no successful run yet). Use this to see where an incremental tap will resume from, or to debug why a scheduled tap is re-fetching or skipping a window.

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_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden, and it does well: it discloses the returned object shape, the DATRIS_TAP_STATE injection mechanism, and the important edge case that `state` is null for non-incremental taps or taps with no successful run. It omits permission requirements and whether the call errors for unknown tap names, which is why it stops short of 5.

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, front-loaded with the definition, then the return shape, then the null edge case, then the use cases. Every clause carries information an agent needs; nothing is restated from the schema or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no annotations and no output schema, the description compensates by spelling out the returned fields and their null semantics. An agent has everything needed to decide whether to call it and how to interpret the result.

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% for the single `name` parameter, so the schema already documents it fully. The description adds no lookup syntax, naming conventions, or error behavior for the parameter, so the 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 description states a specific verb and resource — reading a tap's incremental-sync bookmark/cursor — and pins down what that means operationally (the value injected as DATRIS_TAP_STATE on the next run). It also names the exact response fields, so an agent can tell this apart from get_tap (metadata) or get_tap_ledger (history) without opening a schema.

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?

It gives two concrete usage scenarios: seeing where an incremental tap will resume, and debugging a scheduled tap that re-fetches or skips a window. What's missing is explicit routing — it never says to use set_tap_state to write a bookmark or get_tap_ledger to inspect past commits, leaving that inference to the agent.

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