Skip to main content
Glama
Abeautifulsnow

TDengine Query MCP Server

get_all_stables

Retrieve all super tables from a TDengine database to analyze database structure and explore available data models for querying.

Instructions

Get all stables.

    Args:
        db_name (Optional[str]): The name of the database. Defaults to None. When the value is None, it means the configured database is used.

    Returns:
        TaosSqlResponse: All stables in the current Taos database.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
db_nameNoThe name of the database. Default is None which means the configured database.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
headYes
rowsYes
statusYes
column_metaYes

Implementation Reference

  • The implementation of the 'get_all_stables' MCP tool handler.
    @mcp.tool(name="get_all_stables")
    def get_all_stables(
        ctx: Context,
        db_name: Optional[str] = Field(
            None,
            description="The name of the database. Default is None which means the configured database.",
        ),
    ) -> TaosSqlResponse:
        """Get all stables.
    
        Args:
            db_name (Optional[str]): The name of the database. Defaults to None. When the value is None, it means the configured database is used.
    
        Returns:
            TaosSqlResponse: All stables in the current Taos database.
        """
    
        taos = ctx.request_context.lifespan_context.client
        if db_name is None or db_name == "":
            db_name = taos.database
    
        result = taos.execute_sql(f"SHOW {db_name}.STABLES;")
    
        return result
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses nothing about read-only status, permission requirements, performance characteristics, or what the TaosSqlResponse contains. The description is purely functional without behavioral context.

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?

Uses standard docstring format (Args/Returns) which is structured and readable. No extraneous text. However, the Returns section is redundant given that an output schema exists and the description appears in the main description field rather than being separated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a single-parameter tool with full schema coverage and output schema present. However, given the lack of annotations and the potential cost/scope of 'get all' operations in database contexts, it could disclose more about safety or result set size.

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 coverage is 100%, establishing baseline 3. The Args section duplicates the schema description almost exactly ('Default is None which means the configured database' vs 'Defaults to None... configured database is used'), adding no additional semantic value like valid naming conventions or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'Get all stables' which clearly identifies the verb and resource, but is essentially a restatement of the function name. It fails to distinguish from sibling tools like query_taos_db_data (which queries data) or get_all_dbs (which gets databases), and does not clarify what a 'stable' (super table) is in this context.

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?

Provides no guidance on when to use this tool versus alternatives like query_taos_db_data or get_field_infos. Does not mention whether to use switch_db first or if db_name parameter obviates that need.

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/Abeautifulsnow/tdengine-mcp'

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