Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_dataset

Retrieve details for a specific Apache Airflow dataset by URI for API v1 inspection; v2 uses Assets.

Instructions

[Tool Role]: Gets details of a specific dataset (v1 API only - v2 uses Assets).

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

Input Schema

NameRequiredDescriptionDefault
dataset_uriYesDataset URI, such as s3://bucket/path; API v1 only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.7.4
    • addedInput schema / properties / dataset_uri / description
      Added value: +"Dataset URI, such as s3://bucket/path; API v1 only."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed2 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dataset_uri / title
      Removed value: -"Dataset Uri"
  5. Addedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says it 'gets details'. It does not state that this is a read-only operation, what happens on an invalid or v2-era URI, or any permission requirements. An output schema exists so return shape needn't be covered, but the mutation/safety profile remains undisclosed.

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?

A single short sentence with the key scope distinction front-loaded; every element (including the v1/v2 note) earns its place. Minor filler in the '[Tool Role]:' prefix, but otherwise efficient.

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 one-parameter read tool with full schema coverage and an output schema, the description supplies the one non-obvious detail (v1 only vs Assets in v2). It is largely sufficient, with only the read-only/error behavior left implicit.

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% and the single parameter's description already documents the URI format and v1-only constraint. The tool description's version note reinforces but does not extend beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (Gets) and resource (details of a specific dataset), which is clear and distinct from list_datasets. The parenthetical note that it is v1-only and v2 uses Assets helps separate it from other retrieval paths, though it doesn't explicitly contrast with siblings like get_dataset_events.

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

Usage Guidelines3/5

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

Usage is implied: fetch details for one dataset. The v1/v2 caveat gives a routing hint away from Assets-based workflows, but there is no explicit statement of when to prefer this over list_datasets or get_dataset_events, nor any prerequisite guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.