Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_integration

Retrieve configuration details for a specific integration type in Coroot, including connection settings and status, to manage monitoring connections.

Instructions

Get specific integration configuration details.

Retrieves the current configuration for a specific integration type, including connection details, settings, and status.

Args: project_id: The project ID integration_type: Type of integration (prometheus, cloudwatch, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
integration_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main MCP tool handler for 'get_integration', decorated with @mcp.tool(). It delegates to the private implementation function.
    @mcp.tool()
    async def get_integration(project_id: str, integration_type: str) -> dict[str, Any]:
        """
        Get specific integration configuration details.
    
        Retrieves the current configuration for a specific integration type,
        including connection details, settings, and status.
    
        Args:
            project_id: The project ID
            integration_type: Type of integration (prometheus, cloudwatch, etc.)
        """
        return await get_integration_impl(project_id, integration_type)
  • Private helper implementation that creates a CorootClient instance and calls its get_integration method to fetch the configuration, with error handling.
        project_id: str, integration_type: str
    ) -> dict[str, Any]:
        """Implementation for get_integration tool."""
        try:
            client = get_client()
            config = await client.get_integration(project_id, integration_type)
            return {"success": True, "config": config}
        except ValueError as e:
            return {"success": False, "error": str(e)}
        except Exception as e:
            return {"success": False, "error": f"Unexpected error: {str(e)}"}
  • CorootClient class method that performs the HTTP GET request to the Coroot API endpoint for retrieving a specific integration's configuration.
    async def get_integration(
        self, project_id: str, integration_type: str
    ) -> dict[str, Any]:
        """Get specific integration configuration.
    
        Args:
            project_id: The project ID
            integration_type: The integration type
    
        Returns:
            Dict containing integration configuration
        """
        response = await self._request(
            "GET", f"/api/project/{project_id}/integrations/{integration_type}"
        )
        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 the full burden of behavioral disclosure. It states the tool retrieves configuration details, implying it's a read-only operation, but doesn't explicitly confirm this or mention any behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the integration doesn't exist. The description adds minimal context beyond the basic purpose, leaving significant gaps in understanding how the tool behaves.

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 well-structured and appropriately sized: it starts with a clear purpose statement, elaborates with a second sentence, and then lists parameters. There's no wasted text, and it's front-loaded with the main functionality. It could be slightly more concise by integrating the parameter explanations into the flow, but overall it's efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 required parameters) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose and parameters adequately. However, with no annotations and incomplete behavioral transparency, there are gaps in understanding permissions or error handling, preventing a score of 5.

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 description includes an 'Args' section that explains both parameters: 'project_id' as 'The project ID' and 'integration_type' as 'Type of integration (prometheus, cloudwatch, etc.)'. With schema description coverage at 0% (titles only, no descriptions), this adds crucial semantic meaning beyond the schema. However, it doesn't provide examples or constraints (e.g., format for project_id, full list of integration types), so it doesn't reach a score of 5.

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: 'Get specific integration configuration details' and 'Retrieves the current configuration for a specific integration type'. It specifies the verb ('Get', 'Retrieves') and resource ('integration configuration details'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_integrations' or 'test_integration', which is why it doesn't reach a score of 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 sibling tools like 'list_integrations' (for listing all integrations) or 'configure_integration' (for modifying configurations), nor does it specify prerequisites or contexts for usage. This lack of comparative guidance leaves the agent to infer usage from the tool name alone.

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