Skip to main content
Glama
manzoor-source

Teradata MCP Server

dba_tableSpace

Read-onlyIdempotent

Shows table-level disk space usage in a Teradata database, ranked by size. Use to find which tables are consuming the most storage.

Instructions

Show table-level disk space usage within a specific Teradata database, ranked by size. Use when the user asks which tables are largest or consuming the most storage within a named database. NEVER call this tool with an empty database_name — if the user's message does not explicitly name a database, ask which database they want before calling. For space allocated to a whole database, use dba_databaseSpace. For total system-wide storage, use dba_systemSpace.

Arguments: database_name - Database name. Required — do not pass empty string. table_name - Table name filter. Leave empty for all tables. top_n - Limit results to top N largest tables by space. Set to 0 for no limit (default: 0). exclude_system - Exclude system databases and tables. Set to 'Y' to exclude, 'N' to include all (default: 'N'). persist - If True, materializes result as a volatile table and returns table name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_nNoLimit results to top N largest tables by space. Set to 0 for no limit (default: 0).
persistNoIf True, materializes result as a volatile table and returns table name
table_nameNoTable name filter. Leave empty for all tables.
database_nameYesDatabase name. Required — do not pass empty string.
exclude_systemNoExclude system databases and tables. Set to 'Y' to exclude, 'N' to include all (default: 'N').N
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds behavioral details: results are sorted by size and the persist parameter materializes result as a volatile table, returning table 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?

Description is well-structured with a clear purpose sentence, usage guidelines, and bulleted arguments. However, the argument list duplicates schema descriptions, making it slightly redundant. Still efficient for 5 parameters.

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?

Given no output schema, the description explains the tool's behavior (ranked space usage) and the persist parameter's effect. It lacks explicit detail on output fields, but the usage scenario is well-covered. Adequate for a query tool.

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 baseline is 3. The description repeats the same parameter descriptions as the schema, adding no new meaning beyond what is already in the schema's property descriptions.

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?

Clearly states the tool shows table-level disk space usage within a specific Teradata database, ranked by size. It specifies verb, resource, and context, and distinguishes from sibling tools like dba_databaseSpace and dba_systemSpace.

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?

Explicitly states when to use (user asks for largest tables in a named database) and when not to (empty database_name), provides instruction to ask for database, and names alternatives (dba_databaseSpace for whole database, dba_systemSpace for system-wide).

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/manzoor-source/teradata-mcp-server-stc'

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