Skip to main content
Glama
veeemlab

@veeemlab/itglue-mcp

by veeemlab

itglue_delete_contact

Delete an IT Glue contact by ID. Requires confirmation token 'DELETE_CONTACT' to proceed.

Instructions

Delete a contact by id. Destructive — requires confirm: "DELETE_CONTACT".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact id.
confirmYesRequired safety token. Pass "DELETE_CONTACT" verbatim to acknowledge this destructive operation. Without it the call is refused.
Behavior4/5

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

Explicitly labels the operation as 'Destructive' and requires a safety token, providing clear behavioral insight without annotations. Does not detail error handling or side effects beyond deletion.

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?

Extremely concise: two sentences front-load the action and critical safety information with no extraneous 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 for a simple delete operation with two parameters. Lacks detail on return value or confirmation of deletion, but sufficient given no output schema and straightforward nature.

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% and the description minimally adds to the schema by reiterating the confirm token requirement. Baseline score of 3 is appropriate as no significant extra meaning is provided.

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 'Delete a contact by id', using a specific verb and resource. Distinguishes from sibling delete tools by specifying the target resource and the required confirm token for destructive operations.

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?

Indicates the tool is destructive and requires a confirm token, which implies it should only be used when intending to permanently delete a contact. However, lacks explicit guidance on when not to use or mention of alternative tools.

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