Skip to main content
Glama
jamesbrink

MCP Server for Coroot

delete_custom_cloud_pricing

Remove custom cloud pricing overrides for a project to revert to default pricing configurations in the Coroot observability platform.

Instructions

Delete custom cloud pricing configuration.

Removes custom pricing overrides and reverts to default pricing.

Args: project_id: Project ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration using @mcp.tool() decorator. This defines the tool entrypoint with input schema in docstring.
    @mcp.tool()
    async def delete_custom_cloud_pricing(project_id: str) -> dict[str, Any]:
        """Delete custom cloud pricing configuration.
    
        Removes custom pricing overrides and reverts to default pricing.
    
        Args:
            project_id: Project ID
        """
        return await delete_custom_cloud_pricing_impl(project_id)  # type: ignore[no-any-return]
  • Server-side tool handler implementation that calls the CorootClient and wraps the response with success status.
    @handle_errors
    async def delete_custom_cloud_pricing_impl(project_id: str) -> dict[str, Any]:
        """Delete custom cloud pricing."""
        client = get_client()
        result = await client.delete_custom_cloud_pricing(project_id)
        return {
            "success": True,
            "message": "Custom cloud pricing deleted successfully",
            "result": result,
        }
  • Core client implementation that sends DELETE request to Coroot API endpoint /api/project/{project_id}/custom_cloud_pricing and handles various response cases.
    async def delete_custom_cloud_pricing(self, project_id: str) -> dict[str, Any]:
        """Delete custom cloud pricing configuration.
    
        Args:
            project_id: Project ID.
    
        Returns:
            Deletion status.
        """
        response = await self._request(
            "DELETE", f"/api/project/{project_id}/custom_cloud_pricing"
        )
    
        # Handle empty response (204 or empty body)
        if response.status_code == 204:
            return {"status": "deleted"}
    
        # Try to parse JSON response
        try:
            content = response.text.strip()
            if not content:
                # Empty response body with 200 status
                return {"status": "deleted"}
            data: dict[str, Any] = response.json()
            return data
        except Exception:
            # If parsing fails, assume success if status code is 2xx
            if 200 <= response.status_code < 300:
                return {"status": "deleted"}
            raise
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 states the tool deletes and reverts to defaults, which implies a destructive mutation, but doesn't disclose behavioral traits such as required permissions, whether the action is reversible, potential side effects, or rate limits. This leaves significant gaps for safe agent invocation.

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?

The description is appropriately sized with three sentences: a purpose statement, effect explanation, and parameter documentation. It's front-loaded with the core action, and each sentence adds value without redundancy. Minor improvements could include integrating the 'Args' more seamlessly.

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

Completeness3/5

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

Given the tool's complexity (destructive mutation with 1 parameter), no annotations, and an output schema present (which reduces need to describe returns), the description is moderately complete. It covers purpose and parameter basics but lacks behavioral details like permissions or reversibility, making it adequate but with clear gaps for safe use.

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 description coverage is 0%, but the description includes an 'Args' section that documents the single parameter 'project_id'. This adds meaning beyond the bare schema, explaining it's a 'Project ID'. However, it doesn't provide format details, examples, or constraints, so it partially compensates for the low coverage.

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 tool's purpose with a specific verb ('Delete') and resource ('custom cloud pricing configuration'), and explains the effect ('Removes custom pricing overrides and reverts to default pricing'). It doesn't explicitly differentiate from sibling tools like 'update_custom_cloud_pricing' or 'get_custom_cloud_pricing', but the action is distinct enough to infer usage.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_custom_cloud_pricing' for modifications or 'get_custom_cloud_pricing' for viewing. It mentions reverting to default pricing, which implies usage after custom pricing is set, but lacks explicit context, prerequisites, or exclusions.

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