Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

plot_pie_chart

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

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 Required Argument. Specifies the name of the table to generate the donut plot. Types: str
labelsYes Required Argument. Specifies the labels to be used for the line plot. Types: str
columnYes Required Argument. Specifies the column to be used for generating the line plot. Types: str

Tool Definition Quality

C2/5.0
Behavior1/5

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

No annotations provided. The description does not disclose any behavioral traits such as error handling, empty data behavior, or dependencies beyond parameter definitions. Relies entirely on schema.

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?

The description is overly long and duplicates the schema verbatim. It could be condensed to one clear sentence. The structure is rambling.

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 is provided, yet the description only states 'dict' with no details on keys or structure. Missing information about errors, defaults, or behavioral constraints. Inadequate given the tool's apparent complexity.

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

Parameters2/5

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

Schema coverage is 100% but the description adds only redundant information. It also introduces confusion by calling 'column' a line plot parameter. Almost no semantic value beyond the schema.

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?

The description states it generates a pie chart, but the explanation of parameters is confusing, mixing 'labels and columns' and referencing 'line plot' incorrectly. The title is missing. It is clear enough but lacks precision.

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 pie chart tool versus sibling chart tools (line, polar, radar). No context on appropriate data types or scenarios.

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/Teradata/teradata-mcp-server'

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