Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Dba Databasespace

dba_databaseSpace
Read-onlyIdempotent

Check disk space usage and allocation for a specific Teradata database. Provide the database name to see how much space it is using or has allocated.

Instructions

Show disk space allocation for a specific named Teradata database. Use when the user asks how much space a particular database is using or how much has been allocated to it. If no database name is provided, ask for clarification — do not call with an empty database name. For table-level breakdowns within a database, use dba_tableSpace. For system-wide totals across all databases, use dba_systemSpace.

Arguments: database_name - Database name. Required — do not pass empty string. 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
database_nameYesDatabase name. 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. Leave empty or omit for all databases."New value: +"Database name. Required — do not pass empty string."
    • addedInput schema / required
      Added value: +[
+  "database_name"
+]
  2. Changed8 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / database_name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / database_name / default
      Added value: +""
    • addedInput schema / properties / database_name / description
      Added value: +"Database name. Leave empty or omit 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 / required
      Removed value: -[
-  "database_name"
-]
  3. Changed1 schema field changedv1.0.0
    • removedInput schema / title
      Removed value: -"handle_dba_databaseSpaceArguments"
  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 mark the tool as read-only and idempotent. The description adds useful behavioral context beyond annotations by requiring clarification for missing database names and explaining that persist materializes a volatile table and returns its name. 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?

The description is well-structured and front-loaded with the main purpose, followed by usage guidance and parameter notes. It is slightly redundant with the schema's parameter descriptions, but every sentence earns its place.

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 simple two-parameter read-only tool with full schema coverage and no output schema, the description is nearly complete. It covers scope, sibling alternatives, required argument behavior, and the persist side effect; only the exact return format is left unspecified.

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 schema already documents both parameters. The description repeats the parameter details rather than adding meaning beyond the schema, which meets the baseline but does not exceed it.

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 states a specific verb and resource: 'Show disk space allocation for a specific named Teradata database.' It also explicitly differentiates itself from sibling tools dba_tableSpace and dba_systemSpace, so an agent can distinguish it immediately.

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 provides explicit when-to-use guidance ('when the user asks how much space a particular database is using'), a clear guardrail ('If no database name is provided, ask for clarification — do not call with an empty database name'), and names alternative tools for different scopes.

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