Skip to main content
Glama
devhelmhq

DevHelm MCP Server

Official
by devhelmhq

delete_tag

Delete a tag from your monitoring system by specifying its unique tag ID. This removes the tag from all associated resources.

Instructions

Delete a tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tag_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `delete_tag` tool handler. Accepts `tag_id` (string) and optional `api_token`. Calls `get_client(api_token).tags.delete(tag_id)` via the DevHelm SDK and returns a success message "Tag deleted successfully." on success, or raises a tool error via `raise_tool_error` on `DevhelmError`.
    @mcp.tool()
    def delete_tag(tag_id: str, api_token: str | None = None) -> str:
        """Delete a tag."""
        try:
            get_client(api_token).tags.delete(tag_id)
            return "Tag deleted successfully."
        except DevhelmError as e:
            raise_tool_error(e)
  • The `register` function in `tags.py` that registers `delete_tag` (and other tag tools) with the FastMCP server via the `@mcp.tool()` decorator.
    def register(mcp: FastMCP) -> None:
  • The `server.py` registration loop that calls `mod.register(mcp)` for all tool modules, including `tags`, which registers `delete_tag` with the MCP server.
    for mod in ALL_TOOL_MODULES:
        mod.register(mcp)
  • The function signature defines the input schema for `delete_tag`: a required `tag_id: str` and an optional `api_token: str | None`.
    def delete_tag(tag_id: str, api_token: str | None = None) -> str:
  • The test file lists `"delete_tag"` as one of the expected registered tool names, confirming it's tracked in tool registration tests.
    "delete_tag",
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It fails to mention whether deletion is irreversible, cascading effects, or permission requirements. The single sentence is insufficient.

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

Conciseness2/5

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

The description is extremely concise at three words, but this is under-specification. It lacks necessary details, making it insufficient for an agent to use correctly.

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

Completeness2/5

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

Given the simplicity of a delete operation, the description should at least mention return values, error states, or idempotency. It does not, leaving the agent with incomplete information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the 'tag_id' parameter. The schema itself is minimal, and the description adds no semantic meaning beyond what the schema provides.

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

Purpose4/5

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

The description clearly states the verb 'Delete' and the resource 'a tag', which matches the tool name. However, it does not differentiate from other tag-related tools like 'update_tag' or 'create_tag', though the verb itself is distinct.

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 effects of deletion. The agent receives no context for decision-making.

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/devhelmhq/mcp-server'

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