Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_tap

Retrieve a tap's static configuration, schedule, target pipeline, and generated Python script. Use it for config inspection only; check run status or history with status and log tools.

Instructions

Get a tap's static definition: configuration, schedule, target pipeline, and the generated Python script content. This is config-only — it returns the SAME data on every call and tells you NOTHING about run state. Do NOT call this to check whether a run is finished or to poll for completion — repeatedly calling get_tap after run_tap is a bug, the response will never change to reflect ingestion progress. For run status: call get_pipeline_status(publisher_token=...) (token comes from the run_tap response or from a get_tap_logs entry). For run history: call get_tap_logs.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap to retrieve

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?

With no annotations provided, the description carries the full burden and does it well: it discloses idempotent behavior ("returns the SAME data on every call"), that it reveals nothing about run state, and that the response will never change. The only gap is return-format specifics such as what the script content field looks like, which is minor for a single-resource read.

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?

Well front-loaded: the definition of what the tool returns comes first, then the negative guidance and alternatives. It is slightly repetitive, restating the same idempotency warning twice ("SAME data on every call" and "the response will never change"), but the emphasis is defensible given the cost of the misuse it prevents.

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 output schema, the description covers what comes back, that it is static, and which sibling to use for each adjacent need. An agent has everything required to call it correctly and to avoid the primary failure mode.

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?

There is one required parameter with 100% schema description coverage, so the schema already documents it fully; baseline is 3. The description adds no extra syntax, naming-convention, or resolution detail for the `name` argument beyond what the schema states.

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 a tap's static definition") and enumerates the returned contents: configuration, schedule, target pipeline, and generated Python script. The word "static" plus "config-only" distinguishes it immediately from state/status siblings like get_tap_state and get_pipeline_status.

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?

Explicitly names the anti-pattern (calling get_tap after run_tap to poll for completion) and routes the agent to the correct alternatives: get_pipeline_status for run status and get_tap_logs for run history. It even explains where the publisher_token argument comes from, so the handoff is actionable.

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