Skip to main content
Glama
jamesbrink

MCP Server for Coroot

update_custom_cloud_pricing

Set custom pricing for cloud resources to override default costs in Coroot monitoring projects.

Instructions

Update custom cloud pricing configuration.

Sets custom pricing for cloud resources to override default pricing.

Args: project_id: Project ID pricing: Custom pricing configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
pricingYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function decorated with @mcp.tool(), which registers it and defines input schema via type hints and docstring. Calls internal impl.
    @mcp.tool()
    async def update_custom_cloud_pricing(
        project_id: str, pricing: dict[str, Any]
    ) -> dict[str, Any]:
        """Update custom cloud pricing configuration.
    
        Sets custom pricing for cloud resources to override default pricing.
    
        Args:
            project_id: Project ID
            pricing: Custom pricing configuration
        """
        return await update_custom_cloud_pricing_impl(project_id, pricing)  # type: ignore[no-any-return]
  • Internal helper implementation that invokes the CorootClient method and formats the standardized error/success response.
    @handle_errors
    async def update_custom_cloud_pricing_impl(
        project_id: str, pricing: dict[str, Any]
    ) -> dict[str, Any]:
        """Update custom cloud pricing."""
        client = get_client()
        result = await client.update_custom_cloud_pricing(project_id, pricing)
        return {
            "success": True,
            "message": "Custom cloud pricing updated successfully",
            "pricing": result,
        }
  • Coroot API client method that performs the HTTP POST request to the Coroot server to update custom cloud pricing configuration.
    async def update_custom_cloud_pricing(
        self, project_id: str, pricing: dict[str, Any]
    ) -> dict[str, Any]:
        """Update custom cloud pricing configuration.
    
        Args:
            project_id: Project ID.
            pricing: Custom pricing configuration.
    
        Returns:
            Updated pricing configuration.
        """
        response = await self._request(
            "POST", f"/api/project/{project_id}/custom_cloud_pricing", json=pricing
        )
        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 the full burden. It states the tool 'Updates' and 'Sets custom pricing', implying a mutation operation, but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to existing pricing. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 and front-loaded: the first sentence states the purpose, the second elaborates, and the 'Args' section lists parameters clearly. There's no wasted text, and the structure is logical. It could be slightly more concise by integrating the args into the main text, but it's efficient overall.

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 (mutation with nested objects), no annotations, and 0% schema coverage, the description is moderately complete. It explains the purpose and parameters at a high level, and an output schema exists (per context signals), so return values needn't be described. However, it lacks details on behavioral aspects and parameter formats, making it adequate but with clear gaps for a mutation tool.

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%, so the schema provides no parameter descriptions. The description adds minimal semantics by listing 'project_id: Project ID' and 'pricing: Custom pricing configuration', which clarifies the purpose of each parameter. However, it doesn't explain the format, constraints, or examples (e.g., what 'pricing' object should contain), leaving gaps. With 0% coverage, the description compensates partially but not fully.

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 specific verb ('Update') and resource ('custom cloud pricing configuration'), and explains it 'Sets custom pricing for cloud resources to override default pricing.' This distinguishes it from siblings like 'get_custom_cloud_pricing' (read) and 'delete_custom_cloud_pricing' (delete). However, it doesn't explicitly differentiate from other update tools (e.g., 'update_project_settings'), so it's not a perfect 5.

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. It doesn't mention prerequisites (e.g., needing an existing project), when not to use it (e.g., for default pricing), or compare it to sibling tools like 'get_custom_cloud_pricing' or 'delete_custom_cloud_pricing'. Usage is implied only by the tool name and description, with no explicit context.

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