Skip to main content
Glama

update_chart_data

Replace data series in an existing chart by specifying the chart ID and new series with names and values.

Instructions

Replace data series in an existing chart by chart_id.

series: [{"name": str, "values": [float, ...]}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart_idYes
seriesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description minimally states 'Replace data series' without disclosing whether it fully replaces all series, any side effects, permission requirements, or limitations. The tool mutates data, but the description does not elaborate on behavioral traits.

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: two sentences that convey essential information without redundancy. Every sentence serves a purpose.

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?

The description covers the basic operation but does not address the existence of an output schema or relation to sibling tools (e.g., insert chart tools). Given the simple tool, it is minimally adequate but lacks depth.

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?

The description adds structure to the 'series' parameter with a pseudo-schema, compensating for 0% schema coverage. However, 'chart_id' is not explained beyond its name. The added value is moderate.

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

Purpose5/5

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

The description clearly states the action ('Replace data series'), the resource ('existing chart'), and the identifier ('by chart_id'). It distinguishes this tool from insertion chart tools among siblings.

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 (e.g., other chart manipulation tools or insert chart tools). The description lacks context on prerequisites 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/SecurityRonin/docx-mcp'

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