Skip to main content
Glama
jamesbrink

MCP Server for Coroot

update_sso_config

Configure Single Sign-On settings for Coroot observability platform to manage authentication and access control.

Instructions

Update SSO configuration.

Configures Single Sign-On settings for the Coroot instance.

Args: config: SSO configuration settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in CorootClient that performs the HTTP POST request to /api/sso endpoint with the provided config to update SSO settings.
    async def update_sso_config(self, config: dict[str, Any]) -> dict[str, Any]:
        """Update SSO configuration.
    
        Args:
            config: SSO configuration settings.
    
        Returns:
            Updated SSO configuration.
        """
        response = await self._request("POST", "/api/sso", json=config)
        data: dict[str, Any] = response.json()
        return data
  • FastMCP tool registration decorator @mcp.tool() that exposes the update_sso_config tool, defining its input schema via type hints and docstring.
    @mcp.tool()
    async def update_sso_config(config: dict[str, Any]) -> dict[str, Any]:
        """Update SSO configuration.
    
        Configures Single Sign-On settings for the Coroot instance.
    
        Args:
            config: SSO configuration settings
        """
        return await update_sso_config_impl(config)  # type: ignore[no-any-return]
  • Helper implementation wrapper that invokes the client handler, handles errors via decorator, and formats the standardized MCP response.
    async def update_sso_config_impl(config: dict[str, Any]) -> dict[str, Any]:
        """Update SSO configuration."""
        client = get_client()
        result = await client.update_sso_config(config)
        return {
            "success": True,
            "message": "SSO configuration updated successfully",
            "config": result,
        }
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 of behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't disclose critical behavioral traits such as whether this requires admin permissions, if it's idempotent, what happens on failure, or if it affects existing users. It adds minimal 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, with the core purpose stated first ('Update SSO configuration') followed by a brief elaboration. The Args section is included but adds little value due to its vagueness. There's minimal waste, though the structure could be improved by integrating the parameter note 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 complexity (mutation tool with nested object parameters and no annotations), the description is incomplete. It states the purpose but lacks usage guidelines, detailed parameter semantics, and behavioral context. The presence of an output schema reduces the need to describe return values, but other gaps remain significant for a tool that modifies critical authentication settings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, with one required parameter 'config' of type object with no defined properties. The description adds minimal semantics by labeling it as 'SSO configuration settings', but this is vague and doesn't compensate for the lack of schema details. It fails to explain what specific settings are expected (e.g., SAML/OIDC parameters), leaving the parameter largely undocumented.

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 ('Update') and resource ('SSO configuration'), and it elaborates on what SSO configuration means ('Configures Single Sign-On settings for the Coroot instance'). This distinguishes it from general configuration tools by specifying the SSO domain. However, it doesn't explicitly differentiate from the sibling 'get_sso_config' tool, which is a related read operation.

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 admin permissions), when not to use it, or how it relates to the sibling 'get_sso_config' tool for reading existing configuration. The context is implied (updating SSO settings) but lacks explicit usage instructions.

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