Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata

plot_line_chart

Read-onlyIdempotent

Create a line chart from a Teradata table by specifying a label column for the x-axis and one or more columns for the y-axis.

Instructions

Function to generate a line plot for labels and columns. Columns mentioned in labels are used for x-axis and columns are used for y-axis.

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

columns:
    Required Argument.
    Specifies the column to be used for generating the line plot.
    Types: List[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
columnsYes Required Argument. Specifies the column to be used for generating the line plot. Types: List[str]
Behavior2/5

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

Annotations already indicate read-only and idempotent behavior. The description does not add any additional behavioral traits, such as data requirements, side effects, or limitations. It merely restates the purpose.

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

Conciseness3/5

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

The description is structured but contains redundant formatting (all-caps headers, repeated parameter details) and a typo ('donut plot'). It could be more concise while retaining key information.

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?

No output schema is provided, and the description only says 'RETURNS: dict' without explaining what the dictionary contains (e.g., image data, file path). Sibling tools exist, but no comparison or prerequisites are given.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaning by clarifying that 'labels' are used for the x-axis and 'columns' for the y-axis, which is not stated in the schema descriptions. This helps the agent understand parameter roles beyond the schema.

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 states 'generate a line plot for labels and columns', clearly indicating the resource (line plot) and action. The tool name aligns, and it is distinct from sibling plotting tools (pie, polar, radar). However, a typo in the parameter description refers to 'donut plot', which could cause minor confusion.

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 is provided on when to use this tool versus alternatives like plot_pie_chart or when not to use it. The description only implies usage through the tool name and plot type, lacking explicit context for selection.

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