Skip to main content
Glama

delete-chart

Remove a chart from PI Dashboard by providing its chart ID.

Instructions

Delete a chart

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesChart ID

Implementation Reference

  • build/index.js:815-833 (registration)
    Registration of the 'delete-chart' tool using server.tool() with schema and handler inline.
    server.tool("delete-chart", "Delete a chart", {
        id: z.number().describe("Chart ID")
    }, async ({ id }) => {
        try {
            await authenticatedRequest(`/charts/${id}`, "DELETE");
            return {
                content: [{
                        type: "text",
                        text: `Chart with ID ${id} successfully deleted.`
                    }]
            };
        }
        catch (error) {
            return {
                isError: true,
                content: [{ type: "text", text: `Error deleting chart: ${getErrorMessage(error)}` }]
            };
        }
    });
  • Input schema: requires an 'id' parameter of type number (z.number()), described as 'Chart ID'.
    id: z.number().describe("Chart ID")
  • Handler function that sends a DELETE request to /charts/{id} via authenticatedRequest, then returns success or error.
    }, async ({ id }) => {
        try {
            await authenticatedRequest(`/charts/${id}`, "DELETE");
            return {
                content: [{
                        type: "text",
                        text: `Chart with ID ${id} successfully deleted.`
                    }]
            };
        }
        catch (error) {
            return {
                isError: true,
                content: [{ type: "text", text: `Error deleting chart: ${getErrorMessage(error)}` }]
            };
        }
    });
Behavior2/5

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

No annotations exist, and the description fails to disclose behavioral traits such as permament deletion, dependencies, or required permissions. For a destructive action, this gap is significant.

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

Conciseness4/5

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

The description is extremely concise at three words, but this conciseness comes at the cost of missing valuable context. It could be improved with minimal additions.

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?

Given the simple nature of the tool (one param, no output), the description is partially complete, but lacks behavioral transparency. It does not fully equip an agent to use it correctly.

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%, and the description adds no additional meaning beyond the schema's label 'Chart ID'. Baseline of 3 is appropriate.

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 tool deletes a chart, with a specific verb and resource. Sibling tools like delete-category are differentiated by the resource type, making purpose unambiguous.

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, nor any prerequisites or conditions for deletion. The description is silent on context.

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/mingzilla/pi-api-mcp-server'

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