Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

get_dataset

Retrieve datasets from Apache Airflow deployments by specifying their URI, enabling data access for workflow automation and analysis.

Instructions

Get a dataset by URI

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYes

Implementation Reference

  • Handler function that executes the 'get_dataset' tool: fetches dataset by URI from Airflow API and returns as text content.
    async def get_dataset(
        uri: str,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        response = dataset_api.get_dataset(uri=uri)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registration tuple for the 'get_dataset' tool within the list returned by get_all_functions().
    (get_dataset, "get_dataset", "Get a dataset by URI", True),
  • src/main.py:10-10 (registration)
    Import of the function that provides the list of dataset tools, including get_dataset.
    from src.airflow.dataset import get_all_functions as get_dataset_functions
  • src/main.py:28-28 (registration)
    Mapping APIType.DATASET to get_dataset_functions for loading tools.
    APIType.DATASET: get_dataset_functions,
  • src/main.py:90-92 (registration)
    Code that iterates over functions (including get_dataset) and registers them as MCP tools using app.add_tool.
    for func, name, description, *_ in functions:
        app.add_tool(func, name=name, description=description)
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Get a dataset by URI' without detailing what 'Get' involves (e.g., read-only operation, potential side effects, authentication needs, rate limits, or error handling). This leaves critical behavioral traits unspecified for a tool with unknown complexity.

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?

The description is a single, efficient sentence ('Get a dataset by URI') that is front-loaded with the core action. There is no wasted text, making it appropriately sized for the minimal information provided.

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

Completeness2/5

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

Given the tool's complexity is unknown, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on what 'Get' returns, error conditions, or behavioral context, making it inadequate for effective tool selection and invocation by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter ('uri') with 0% description coverage, and the description adds minimal meaning by specifying 'by URI'. However, it doesn't explain the URI format, expected values, or constraints, failing to compensate for the low schema coverage. This leaves the parameter semantics largely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get a dataset by URI' clearly states the verb ('Get') and resource ('dataset'), but it's vague about what 'Get' entails (e.g., retrieve metadata, fetch content, or download). It distinguishes from siblings like 'get_datasets' (plural) by focusing on a single dataset, but lacks specificity on the dataset type or context.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't explain if this is for retrieving a specific dataset identified by URI, as opposed to 'get_datasets' for listing multiple datasets or other sibling tools for related operations. The description implies usage by mentioning 'by URI' but offers no explicit context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikhil-ganage/mcp-server-airflow-token'

If you have feedback or need assistance with the MCP directory API, please join our Discord server