Skip to main content
Glama
jamesbrink

MCP Server for Coroot

update_ai_config

Configure AI provider settings to enhance root cause analysis in the Coroot observability platform by updating API keys and model selections.

Instructions

Update AI provider configuration.

Configures AI provider settings for enhanced root cause analysis.

Args: config: AI provider settings (API keys, model selection, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation in CorootClient: performs HTTP POST to /api/ai with the provided config and returns the updated configuration.
    async def update_ai_config(self, config: dict[str, Any]) -> dict[str, Any]:
        """Update AI provider configuration.
    
        Args:
            config: AI provider settings.
    
        Returns:
            Updated AI configuration.
        """
        response = await self._request("POST", "/api/ai", json=config)
        data: dict[str, Any] = response.json()
        return data
  • MCP tool registration: @mcp.tool() decorator registers the update_ai_config tool, with input schema dict[str, Any] and description.
    @mcp.tool()
    async def update_ai_config(config: dict[str, Any]) -> dict[str, Any]:
        """Update AI provider configuration.
    
        Configures AI provider settings for enhanced root cause analysis.
    
        Args:
            config: AI provider settings (API keys, model selection, etc.)
        """
        return await update_ai_config_impl(config)  # type: ignore[no-any-return]
  • Helper implementation: wraps client call, adds success message and error handling via @handle_errors decorator.
    async def update_ai_config_impl(config: dict[str, Any]) -> dict[str, Any]:
        """Update AI configuration."""
        client = get_client()
        result = await client.update_ai_config(config)
        return {
            "success": True,
            "message": "AI configuration updated successfully",
            "config": result,
        }
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 describe permissions needed, whether changes are reversible, rate limits, or what the response includes. For a configuration tool with zero annotation coverage, this leaves significant behavioral gaps.

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 efficiently structured with a clear purpose statement, context, and parameter explanation in three sentences. It's front-loaded with the main action and avoids unnecessary verbiage, though the parameter section could be slightly more detailed given the complexity.

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 an output schema present (which reduces need to describe returns), the description is moderately complete. It covers purpose and basic parameter semantics but lacks behavioral details and usage guidelines, making it adequate but with clear gaps for an update operation.

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?

The schema description coverage is 0%, so the description must compensate. It adds a brief explanation of the 'config' parameter ('AI provider settings (API keys, model selection, etc.)'), which provides some semantic context beyond the bare schema. However, with 1 parameter and nested objects, this is minimal—baseline 3 is appropriate as it adds value but doesn't fully detail the structure 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 tool's purpose as 'Update AI provider configuration' and specifies it's for 'enhanced root cause analysis', providing a specific verb ('Update'), resource ('AI provider configuration'), and context. However, it doesn't explicitly differentiate from sibling tools like 'configure_integration' or 'get_ai_config', which would be needed for a perfect score.

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 'configure_integration' or 'get_ai_config'. It mentions the context ('enhanced root cause analysis') but doesn't specify prerequisites, exclusions, or compare to sibling tools, leaving the agent with minimal usage direction.

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