Skip to main content
Glama

delete_macro_tool

Delete a macro from a grandMA2 console's macro pool. This destructive operation permanently removes the macro.

Instructions

Delete a macro from the macro pool.

WARNING: This is a destructive operation that permanently removes the macro.

Args:
    macro_id: Macro number to delete
    pool: Macro pool number (default: 1)

Returns:
    str: Operation result message with warnings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
macro_idYes
poolNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses the destructive nature of the operation ('permanently removes the macro') and mentions the return type (result message with warnings). No annotations exist, so the description carries the full burden and does so adequately.

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?

Concise with a clear structure: action statement, warning, parameter descriptions, and return type. No unnecessary words.

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

Completeness4/5

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

Adequate coverage for a simple delete tool: describes operation, parameters, and return. With no annotations and an output schema, the description provides sufficient context.

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?

Adds meaning beyond the input schema by describing macro_id as 'Macro number to delete' and pool as 'Macro pool number (default: 1)'. With 0% schema coverage, this compensates well.

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?

Clearly states the action ('Delete a macro') and the resource ('macro pool'). Distinguishes from sibling tools like create_macro, run_macro, and list_macros by specifying deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for usage: deleting a macro permanently. The warning about destructiveness implies caution, but no explicit alternatives or when-not-to-use guidance is given.

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/chienchuanw/gma2-mcp'

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