Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Dba Tableusageimpact

dba_tableUsageImpact
Read-onlyIdempotent

Identify users and tables driving query and resource activity in a Teradata database. Requires a database name to reveal top load contributors.

Instructions

Identify which users and tables are driving the most query and resource activity within a specific Teradata database. Use when the user asks who is hitting a named database hardest, which users are most active, or which tables generate the most load. ONLY call when the user has specified a database name — if no database name appears in the message, ask for clarification. For system-wide CPU, IO, and memory metrics by time period or application, use dba_resusageSummary instead.

Arguments: database_name - Database name to analyze. Required — do not pass empty string. user_name - User name to analyze. Leave empty for all users. 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
user_nameNoUser name to analyze. Leave empty for all users.
database_nameYesDatabase name to analyze. Required — do not pass empty string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • removedInput schema / properties / database_name / default
      Removed value: -""
    • changedInput schema / properties / database_name / description
      Previous value: -"Database name to analyze. Leave empty for all databases."New value: +"Database name to analyze. Required — do not pass empty string."
    • addedInput schema / required
      Added value: +[
+  "database_name"
+]
  2. Changed12 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / database_name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / database_name / default
      Previous value: -nullNew value: +""
    • addedInput schema / properties / database_name / description
      Added value: +"Database name to analyze. Leave empty for all databases."
    • removedInput schema / properties / database_name / title
      Removed value: -"Database Name"
    • addedInput schema / properties / database_name / type
      Added value: +"string"
    • 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 / user_name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedInput schema / properties / user_name / default
      Previous value: -nullNew value: +""
    • addedInput schema / properties / user_name / description
      Added value: +"User name to analyze. Leave empty for all users."
    • removedInput schema / properties / user_name / title
      Removed value: -"User Name"
    • addedInput schema / properties / user_name / type
      Added value: +"string"
  3. Changed1 schema field changedv1.0.0
    • removedInput schema / title
      Removed value: -"handle_dba_tableUsageImpactArguments"
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavior beyond annotations: the persist parameter's side effect of materializing a volatile table and returning its name, plus the guardrail to ask for a database name when missing. No contradiction with annotations.

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?

Purpose and usage guidance are front-loaded and tight, with an explicit alternative and guardrail. The 'Arguments' section is redundant with the input schema, which is a minor efficiency loss, but it does not bloat the description significantly.

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 description is largely complete for a read-only analytics tool: it states purpose, triggers, prerequisites, and the behavior of the persist flag. It does not describe the normal (non-persist) return value shape, but given the clear purpose and annotations, this is not a critical gap.

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 baseline is 3. The description repeats the parameter documentation without adding deeper meaning beyond telling the agent that database_name is required and must not be empty; this adds little over 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 opens with a specific verb and resource: 'Identify which users and tables are driving the most query and resource activity within a specific Teradata database.' It clearly differentiates the tool from siblings by scoping to a named database and by naming the alternative for system-wide metrics.

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?

Explicit trigger conditions are given ('who is hitting a named database hardest, which users are most active, or which tables generate the most load'), a hard precondition is stated (database name required, else ask for clarification), and an alternative tool, dba_resusageSummary, is named for different use cases.

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