Skip to main content
Glama
Sign In
MCP-Airflow-API

MCP-Airflow-API

by call518
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

all_dag_event_summary

Summarizes event logs across all DAGs to provide an overview of cluster activity and DAG run history.

Instructions

[Tool Role]: Provides summary of event logs across all DAGs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.7.2
  2. Removedv3.6.5
  3. Changed1 schema field changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'summary' but does not disclose what the summary contains (e.g., counts, time ranges, aggregation), any side effects, or access requirements.

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?

Single sentence is concise and front-loaded with the action. However, it could be slightly more informative without being verbose.

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 name and many siblings, the description should clarify what the summary includes and how it differs. It is too minimal for adequate completeness.

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?

No parameters exist; schema coverage is 100%. The baseline of 4 is appropriate as the description adds no parameter info but is not needed.

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?

The description states it provides a summary of event logs across all DAGs, which is a clear verb+resource. It distinguishes from siblings like 'list_event_logs' (detailed logs) and 'all_dag_import_summary' (import summaries), though not explicitly.

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 on when to use this tool versus alternatives. Does not specify exclusions, prerequisites, or when to prefer other tools like 'list_event_logs' for detailed logs.

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