Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Dba Flowcontrol

dba_flowControl
Read-onlyIdempotent

Identify when and how much Teradata throttled or delayed queries due to resource constraints, providing flow control event details for a given date range.

Instructions

Report Teradata workload management flow control events showing when and how much the system throttled or delayed queries due to resource constraints. Use when the user asks about system throttling, flow control delays, or how often the workload manager imposed restrictions. For how long individual users personally waited in queues, use dba_userDelay instead.

Arguments: start_date - The start date for the query range in YYYY-MM-DD format. end_date - The end date for the query range in YYYY-MM-DD format. persist - If True, materializes result as a volatile table and returns table name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persistNoIf True, materializes result as a volatile table and returns table name
end_dateYesThe end date for the query range in YYYY-MM-DD format.
start_dateYesThe start date for the query range in YYYY-MM-DD format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / end_date / title
      Removed value: -"End Date"
    • addedInput schema / properties / persist
      Added value: +{
+  "default": false,
+  "description": "If True, materializes result as a volatile table and returns table name",
+  "type": "boolean"
+}
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
  2. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / end_date / description
      Added value: +"The end date for the query range in YYYY-MM-DD format."
    • addedInput schema / properties / start_date / description
      Added value: +"The start date for the query range in YYYY-MM-DD format."
    • removedInput schema / title
      Removed value: -"_dynamic_toolArguments"
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds that this is a system-level report rather than a per-user delay report, and mentions the persist behavior of materializing a volatile table. However, this is also present in the input schema and no additional behavioral traits like required privileges or side effects are disclosed beyond what annotations already imply.

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?

The description is well-structured: the first sentence states purpose, the second gives usage context, and the third identifies the sibling alternative. The Arguments list is redundant with the schema but remains brief and scannable. No wasted words, though duplication with the input schema prevents a perfect score.

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?

The tool is a simple read-only reporting tool with three parameters and no output schema. The description covers what the tool does, when to use it, which sibling to use instead, and all parameters. It does not describe the exact return fields, but the phrase 'showing when and how much' gives a reasonable indication. Overall, an agent has enough to invoke the tool correctly.

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 description coverage is 100%, so the input schema already documents start_date, end_date, and persist. The description's Arguments section simply repeats those descriptions verbatim, adding no new meaning or clarifying detail beyond the 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?

The description uses a specific verb and resource: 'Report Teradata workload management flow control events' and adds the scope 'showing when and how much the system throttled or delayed queries due to resource constraints.' It also differentiates from the sibling dba_userDelay by explicitly noting that individual user queue waits are not covered.

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?

The description states explicit trigger conditions: 'Use when the user asks about system throttling, flow control delays, or how often the workload manager imposed restrictions.' It also names the alternative for the excluded case: 'For how long individual users personally waited in queues, use dba_userDelay instead.' This leaves no ambiguity about tool selection.

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