Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_taps

List all taps with status, target pipeline, schedule, and last run info to quickly assess existing data ingestion and avoid redundant API suggestions.

Instructions

List all taps with their status, target pipeline, schedule, and last run info. CALL THIS FIRST (alongside list_pipelines) on any data-related user request — the user's existing taps often reveal what's already being pulled and where, which short-circuits the entire 'should I suggest an external API?' conversation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_taps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does disclose the shape of what comes back (status, target pipeline, schedule, last run info) and that it is a whole-collection read, but says nothing about ordering, pagination, empty-state behavior, or permissions — gaps that matter for a zero-annotation tool.

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?

Two sentences, with the actual behavior front-loaded before the guidance. The second sentence is long and partly rhetorical (the quoted 'should I suggest an external API?' aside) — persuasive rather than strictly informative — but it still earns most of its length by establishing call-first ordering.

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?

For a parameterless read tool with no output schema, the description is nearly sufficient: it enumerates the returned fields and the call-ordering context. It would be complete with a word on volume or ordering, but nothing essential to correct invocation is missing.

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?

The schema has zero parameters, so the baseline is 4. The description's 'List all taps' correctly confirms there is no filtering or pagination argument, consistent with the empty schema.

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 ('List all taps') and enumerates what each entry carries: status, target pipeline, schedule, last run info. The pairing instruction with list_pipelines plus the explicit contrast against suggesting an external API makes it clearly distinct from create_tap/delete_tap and the other list_* siblings.

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 an explicit, unconditional trigger: call this first on any data-related user request, and names list_pipelines as a co-call. It also explains the payoff (existing taps reveal what's already ingested), which tells the agent when this tool is the right entry point rather than inferring it.

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