Skip to main content
Glama
BACH-AI-Tools

BachStudio Teradata MCP Server

plot_pie_chart

Generate a pie chart from a Teradata table using specified labels and a data column.

Instructions

Function to generate a pie chart plot for labels and columns. Columns mentioned in labels are used as labels and column is used to plot.

PARAMETERS: table_name: Required Argument. Specifies the name of the table to generate the donut plot. Types: str

labels:
    Required Argument.
    Specifies the labels to be used for the line plot.
    Types: str

column:
    Required Argument.
    Specifies the column to be used for generating the line plot.
    Types: str

RETURNS: dict

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYes
labelsYes
columnYes
Behavior2/5

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

No annotations provided. Description mentions returning a dict but no details on structure or behavior. No disclosure of side effects, authentication needs, or limitations. Relies on vague statement 'generates a pie chart plot'.

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

Conciseness2/5

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

Description is repetitive and contains irrelevant parameter descriptions. The two-sentence overview is clear but the subsequent parameter list is poorly structured and contains errors.

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

Completeness1/5

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

No output schema, no annotations, and low schema coverage. The description fails to explain how parameters relate to the plot (e.g., column type, label format). Incomplete for a tool with three required parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Parameter descriptions are present but misleading (refer to 'line plot' instead of pie chart). They add no real meaning beyond the schema, and the errors reduce clarity.

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

Purpose2/5

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

The description states it generates a pie chart, but parameter descriptions mention 'line plot', indicating copy-paste errors. It does not clearly distinguish from sibling tools like plot_line_chart, plot_polar_chart, or plot_radar_chart.

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?

No guidance on when to use this tool vs alternatives. No mention of prerequisites, context, or exclusions. Sibling tools exist but no differentiation.

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/BACH-AI-Tools/bachstudio-teradata-mcp-server'

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