Skip to main content
Glama
jamesbrink

MCP Server for Coroot

delete_application_category

Remove custom application categories from Coroot monitoring projects to organize and manage your observability data effectively.

Instructions

Delete an application category.

Removes a custom application category. Built-in categories cannot be deleted.

Args: project_id: Project ID name: Category name to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler and registration for 'delete_application_category'. The @mcp.tool() decorator registers the function, and it calls the CorootClient to perform the deletion.
    @handle_errors
    async def delete_application_category_impl(
        project_id: str,
        name: str,
    ) -> dict[str, Any]:
        """Delete an application category."""
        await get_client().delete_application_category(project_id, name)
        return {
            "success": True,
            "message": f"Application category '{name}' deleted successfully",
        }
    
    
    @mcp.tool()
    async def delete_application_category(
        project_id: str,
        name: str,
    ) -> dict[str, Any]:
        """Delete an application category.
    
        Removes a custom application category. Built-in categories cannot be deleted.
    
        Args:
            project_id: Project ID
            name: Category name to delete
        """
        return await delete_application_category_impl(project_id, name)  # type: ignore[no-any-return]
  • CorootClient helper method that implements the actual API call to delete an application category via POST to /api/project/{project_id}/application_categories with delete action.
    async def delete_application_category(
        self, project_id: str, category_name: str
    ) -> dict[str, Any]:
        """Delete an application category.
    
        Args:
            project_id: Project ID.
            category_name: Name of the category to delete.
    
        Returns:
            Deletion result.
        """
        # For delete, we need to send a minimal valid structure with action and id
        data = {
            "action": "delete",
            "id": category_name,
            "name": category_name,  # Required for validation
            "custom_patterns": "",  # Required for validation
        }
        response = await self._request(
            "POST", f"/api/project/{project_id}/application_categories", json=data
        )
        return self._parse_json_response(response)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that built-in categories cannot be deleted, which is useful behavioral context. However, it doesn't mention permissions required, whether deletion is reversible, side effects (e.g., impact on associated applications), or rate limits, leaving significant gaps for a destructive operation.

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 front-loaded with the core purpose, followed by a constraint and parameter details in a structured 'Args' section. Every sentence adds value without redundancy, making it efficient and easy to parse.

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?

Given a destructive tool with no annotations, 2 parameters, and an output schema (which handles return values), the description is reasonably complete. It covers purpose, constraints, and parameter semantics, but lacks behavioral details like auth needs or error cases, leaving some gaps mitigated by the output schema.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining 'project_id' as 'Project ID' and 'name' as 'Category name to delete,' clarifying their roles beyond the schema's basic titles. This covers both parameters adequately, though it could provide more detail on format or constraints.

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 action ('Delete') and resource ('application category'), specifying it removes custom categories while noting built-in ones cannot be deleted. It distinguishes from siblings like 'create_application_category' and 'update_application_category' by focusing on deletion, but doesn't explicitly contrast with other deletion tools like 'delete_dashboard' or 'delete_project'.

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

Usage Guidelines3/5

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

The description implies usage by stating 'Built-in categories cannot be deleted,' which suggests when not to use it, but lacks explicit guidance on when to choose this over alternatives like 'update_application_category' or general deletion tools. No prerequisites or context for use are provided.

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/jamesbrink/mcp-coroot'

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