Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_sso_config

Retrieve Single Sign-On configuration and available roles for the Coroot observability platform to enable secure authentication setup.

Instructions

Get SSO configuration.

Retrieves Single Sign-On (SSO) configuration and available roles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the get_sso_config tool logic: retrieves the CorootClient instance and calls its get_sso_config method to fetch the SSO configuration from the API.
    async def get_sso_config_impl() -> dict[str, Any]:
        """Get SSO configuration."""
        client = get_client()
        config = await client.get_sso_config()
        return {
            "success": True,
            "config": config,
        }
  • Registration of the 'get_sso_config' MCP tool using the @mcp.tool() decorator. This function serves as the entry point for the tool and delegates to the implementation.
    @mcp.tool()
    async def get_sso_config() -> dict[str, Any]:
        """Get SSO configuration.
    
        Retrieves Single Sign-On (SSO) configuration and available roles.
        """
        return await get_sso_config_impl()  # type: ignore[no-any-return]
  • CorootClient helper method that executes the HTTP GET request to the Coroot API endpoint /api/sso to retrieve the SSO configuration data.
    async def get_sso_config(self) -> dict[str, Any]:
        """Get SSO configuration.
    
        Returns:
            SSO configuration and available roles.
        """
        response = await self._request("GET", "/api/sso")
        data: dict[str, Any] = response.json()
        return data
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 mentions retrieving configuration and roles, but lacks details on permissions, rate limits, response format, or error handling. For a read operation 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short, front-loaded sentences with zero waste. It efficiently conveys the core purpose without fluff. Every sentence earns its place by adding value (e.g., clarifying what 'SSO configuration' includes).

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and a read operation that might involve permissions or data sensitivity, it should ideally mention more behavioral context. It's complete enough for basic use but lacks depth.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info, but that's acceptable given the schema fully covers it. Baseline is 4 for zero parameters, as it avoids unnecessary repetition.

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 ('Get', 'Retrieves') and resource ('SSO configuration and available roles'). It distinguishes itself from siblings like 'update_sso_config' by being a read operation, though it doesn't explicitly mention this distinction. The purpose is not vague or tautological.

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?

No guidance is provided on when to use this tool versus alternatives. While it's implied this is for reading SSO configuration (vs. 'update_sso_config' for writing), the description lacks explicit context, prerequisites, or exclusions. Siblings like 'get_roles' might overlap, but no comparison is made.

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