Skip to main content
Glama
veeemlab

@veeemlab/itglue-mcp

by veeemlab

itglue_delete_flexible_asset

Delete a flexible asset by ID using a required confirmation token. This destructive action removes the asset permanently.

Instructions

Delete a flexible asset by id. Destructive — requires confirm: "DELETE_FLEXIBLE_ASSET".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFlexible asset id.
confirmYesRequired safety token. Pass "DELETE_FLEXIBLE_ASSET" verbatim to acknowledge this destructive operation. Without it the call is refused.
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It clearly discloses the destructive nature and the requirement for a confirmation token, ensuring the agent understands the irreversible effect.

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 at two sentences, with no wasted words. It front-loads the action and essential safety information, making it efficient for an agent to parse.

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

Completeness5/5

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

The tool is simple with only two parameters, and the description covers its destructive behavior and required confirmation. No output schema exists, but the description is complete enough for an agent to use the tool 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 coverage is 100%, so the parameters are fully described in the input schema. The description adds no additional meaning beyond what the schema already states, resulting in a baseline score.

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 'Delete a flexible asset by id,' which is a specific verb and resource. It differentiates from sibling tools like itglue_delete_configuration or itglue_delete_contact by the unique asset type.

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?

The description explicitly states that the operation is destructive and requires the confirm token 'DELETE_FLEXIBLE_ASSET'. While it does not provide when-not-to-use guidance or compare with alternatives, it gives clear prerequisites for using the tool.

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/veeemlab/itglue-mcp'

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