Skip to main content
Glama
jamesbrink

MCP Server for Coroot

update_project_settings

Modify project-level settings like retention policies and alerting configurations in the Coroot observability platform to customize monitoring behavior.

Instructions

Update project settings and configuration.

Updates project-level settings such as retention, alerting, etc.

Args: project_id: Project ID settings: Updated project settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
settingsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler and registration for the 'update_project_settings' tool using @mcp.tool() decorator. This is the entry point executed when the tool is called.
    @mcp.tool()
    async def update_project_settings(
        project_id: str, settings: dict[str, Any]
    ) -> dict[str, Any]:
        """Update project settings and configuration.
    
        Updates project-level settings such as retention, alerting, etc.
    
        Args:
            project_id: Project ID
            settings: Updated project settings
        """
        return await update_project_settings_impl(project_id, settings)  # type: ignore[no-any-return]
  • Helper implementation that wraps the CorootClient call and formats the response with success/error handling via @handle_errors decorator.
    async def update_project_settings_impl(
        project_id: str, settings: dict[str, Any]
    ) -> dict[str, Any]:
        """Update project settings."""
        result = await get_client().update_project(project_id, settings)
        return {
            "success": True,
            "message": "Project settings updated successfully",
            "project": result,
        }
  • Core API client method that performs the HTTP POST request to Coroot's /api/project/{project_id} endpoint to update project settings, including name validation.
    async def update_project(
        self, project_id: str, settings: dict[str, Any]
    ) -> dict[str, Any]:
        """Update project settings.
    
        Args:
            project_id: Project ID.
            settings: Updated project settings.
                     Only 'name' field is supported.
                     Name must match pattern: ^[-_0-9a-z]{3,}$
    
        Returns:
            Updated project.
        """
        # Validate project name if provided
        if "name" in settings:
            import re
    
            if not re.match(r"^[-_0-9a-z]{3,}$", settings["name"]):
                raise ValueError(
                    "Project name must contain only lowercase letters, "
                    "numbers, hyphens, and underscores (min 3 chars)"
                )
    
        response = await self._request(
            "POST",
            f"/api/project/{project_id}",
            json=settings,
        )
        data: dict[str, Any] = response.json()
        return data
  • Utility function that lazily initializes and returns the shared CorootClient instance used by all tools.
    def get_client() -> CorootClient:
        """Get or create the client instance.
    
        Raises:
            ValueError: If no credentials are configured.
        """
        global _client
        if _client is None:
            try:
                _client = CorootClient()
            except ValueError as e:
                # Re-raise with more context
                raise ValueError(
                    "Coroot credentials not configured. "
                    "Please set COROOT_BASE_URL and either:\n"
                    "  - COROOT_USERNAME and COROOT_PASSWORD for automatic login\n"
                    "  - COROOT_SESSION_COOKIE for direct authentication\n"
                    "  - COROOT_API_KEY for data ingestion endpoints"
                ) from e
        return _client
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, rate limits, or what happens to unspecified settings. The description adds minimal behavioral context beyond the basic action.

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, followed by elaboration and parameter details. There's minimal redundancy, though the repetition of 'Update' in the first two lines is slightly inefficient. Overall, it's structured and concise.

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 parameters), lack of annotations, and 0% schema coverage, the description is incomplete. It covers the basic action and parameters but misses behavioral details and deeper parameter semantics. The presence of an output schema reduces the need to explain return values, but more context is needed for safe and effective 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%, so the schema provides no parameter details. The description adds basic semantics: 'project_id: Project ID' and 'settings: Updated project settings', which clarifies the purpose of each parameter. However, it doesn't explain the structure or allowed values for 'settings' (a nested object), leaving significant gaps. This partial compensation justifies a baseline score.

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: 'Update project settings and configuration' with examples like 'retention, alerting, etc.' This specifies the verb (update) and resource (project settings/configuration). However, it doesn't explicitly differentiate from sibling tools like 'update_ai_config' or 'update_inspection_config', which also update configurations for different resources.

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), exclusions, or comparisons to sibling tools like 'configure_integration' or 'update_dashboard'. Usage is implied but not explicitly stated.

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