Skip to main content
Glama
startreedata

StarTree MCP Server for Apache Pinot

Official
by startreedata

table-details

Retrieve table size metrics to monitor and optimize data storage in StarTree MCP Server for Apache Pinot by specifying the table name.

Instructions

Get table size details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableNameYesTable name

Implementation Reference

  • MCP tool handler function 'table_details' that executes the tool logic by calling PinotClient.get_table_detail and returning JSON.
    @mcp.tool
    def table_details(tableName: str) -> str:
        """Get table size details"""
        try:
            results = pinot_client.get_table_detail(tableName=tableName)
            return json.dumps(results, indent=2)
        except Exception as e:
            return f"Error: {str(e)}"
  • Helper method in PinotClient that implements the core logic for fetching table size/details via HTTP GET to the Pinot controller's /tables/{tableName}/size endpoint.
    def get_table_detail(
        self,
        tableName: str,
        params: dict[str, Any] | None = None,
    ) -> dict[str, Any]:
        endpoint = PinotEndpoints.TABLE_SIZE.format(tableName)
        url = f"{self.config.controller_url}/{endpoint}"
        logger.debug(f"Fetching table details for {tableName} from: {url}")
        response = self.http_request(url)
        return response.json()
  • Registration of the 'table_details' tool using the @mcp.tool decorator.
    @mcp.tool
    def table_details(tableName: str) -> str:
  • Definition of API endpoints, including TABLE_SIZE used for table-details.
    class PinotEndpoints:
        QUERY_SQL = "query/sql"
        TABLES = "tables"
        SCHEMAS = "schemas"
        TABLE_SIZE = "tables/{}/size"
        SEGMENTS = "segments/{}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read operation, the description doesn't specify what 'size details' includes (e.g., row count, storage size, partitions), whether there are rate limits, authentication requirements, or error conditions. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words, with zero wasted language. It's front-loaded with the core purpose and doesn't include any unnecessary elaboration, making it efficient for quick understanding.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool that presumably returns detailed table information. It doesn't explain what 'size details' encompasses, the format of the response, or any behavioral nuances, leaving the agent with insufficient context to use the tool effectively.

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%, with the single parameter 'tableName' clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for adequate but unremarkable coverage.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'table size details', making the purpose understandable. However, it doesn't distinguish this tool from potential sibling tools like 'get-table-config' or 'segment-metadata-details' that might also retrieve table-related information, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools like 'get-table-config', 'segment-metadata-details', and 'list-tables', there's no indication of what makes 'table-details' unique or when it should be preferred over other table-related tools.

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

Related 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/startreedata/mcp-pinot'

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