Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_tap_logs

Retrieve a tap's last 50 run logs to verify scheduled or manual runs, inspect status, errors, and durations, and recover publisher tokens for tracing data ingestion.

Instructions

Get the run history for a tap. Returns the last 50 run log entries sorted by most recent first, including status, record count, duration, errors, logs, and publisherToken for each run that submitted records to a pipeline. Works for both manual runs (triggered by run_tap) and scheduled runs (triggered by the platform's cron scheduler) — they share the same log. Use this to verify whether a scheduled run fired, whether any recent run's script succeeded, and to recover the publisherToken for any run if you didn't keep the original run_tap response in context. To verify the actual destination ingestion outcome — not just that the script ran — pick the relevant entry and call get_pipeline_status(publisher_token=entry.publisherToken). The tap log only records what the script did; the publisher token is how you trace a run through to whether the data actually landed in the destination.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap to get logs for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses result-set size and ordering (last 50, most recent first), the fields returned per entry, and the non-obvious fact that manual (run_tap) and cron-scheduled runs write to the same log. It does not cover permissions/authorization, log retention, or whether 50 is a hard cap with no pagination, which are the remaining behavioral gaps.

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?

Front-loaded with the resource, result shape, and ordering before moving to usage and cross-tool routing. The closing sentence ('The tap log only records what the script did; the publisher token is how you trace a run...') partially restates the preceding routing instruction, which is the only real redundancy in an otherwise dense and ordered description.

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 one-parameter read tool with no annotations and no output schema, the description supplies everything needed: what comes back, in what order and quantity, what the fields mean, how manual versus scheduled runs relate, and which sibling to call to answer the downstream question. Nothing an agent needs to invoke it correctly or interpret the result is missing.

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 coverage is 100% with a single required 'name' parameter, so the schema already documents it fully. The description only implies the tap identity implicitly ('for a tap') and adds no format, naming convention, or lookup hints beyond the schema, so the baseline of 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?

States a specific verb and resource ('Get the run history for a tap') and immediately specifies the scope and payload: last 50 entries, most recent first, including status, record count, duration, errors, logs, and publisherToken. An agent can distinguish this from get_pipeline_status, which the description explicitly positions as the destination-outcome check rather than the script-run check.

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

Usage Guidelines5/5

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

Gives concrete when-to-use cases (verify a scheduled run fired, check whether a recent run's script succeeded, recover a publisherToken lost from context) and names the alternative plus the exact condition for switching to it: get_pipeline_status(publisher_token=entry.publisherToken) when the question is whether data landed in the destination. It also clarifies that manual and scheduled runs share the same log, which pre-empts a plausible mis-selection.

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