Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_applications_overview

Retrieve a comprehensive overview of all applications in a project, including health status, performance indicators, resource usage, and recent incidents.

Instructions

Get overview of all applications in a project.

Returns a high-level view of all applications including:

  • Application health status

  • Key performance indicators

  • Resource usage

  • Recent incidents

Args: project_id: Project ID query: Search/filter query (optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
queryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'get_applications_overview', decorated with @mcp.tool(). It delegates to the implementation helper.
    @mcp.tool()
    async def get_applications_overview(
        project_id: str,
        query: str | None = None,
    ) -> dict[str, Any]:
        """Get overview of all applications in a project.
    
        Returns a high-level view of all applications including:
        - Application health status
        - Key performance indicators
        - Resource usage
        - Recent incidents
    
        Args:
            project_id: Project ID
            query: Search/filter query (optional)
        """
        return await get_applications_overview_impl(project_id, query)  # type: ignore[no-any-return]
  • Helper implementation that calls the CorootClient's get_applications_overview method and formats the response.
    @handle_errors
    async def get_applications_overview_impl(
        project_id: str,
        query: str | None = None,
    ) -> dict[str, Any]:
        """Get applications overview."""
        overview = await get_client().get_applications_overview(project_id, query)
        return {
            "success": True,
            "overview": overview,
        }
  • CorootClient method that executes the HTTP GET request to retrieve applications overview from the Coroot API.
    async def get_applications_overview(
        self,
        project_id: str,
        query: str | None = None,
    ) -> dict[str, Any]:
        """Get applications overview.
    
        Args:
            project_id: Project ID.
            query: Search/filter query.
    
        Returns:
            Applications overview data.
        """
        params = {}
        if query:
            params["query"] = query
    
        response = await self._request(
            "GET",
            f"/api/project/{project_id}/overview/applications",
            params=params,
        )
        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 returns a high-level view with specific data points (health status, KPIs, etc.), which adds some context beyond the basic 'get' action. However, it lacks critical behavioral details such as whether this is a read-only operation, potential rate limits, authentication requirements, or pagination behavior for large result sets. For a tool with no annotations, this leaves significant 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 well-structured and front-loaded with the core purpose in the first sentence, followed by a bulleted list of return data and a clear parameter explanation. Every sentence earns its place without redundancy, making it efficient and easy to parse.

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 parameters, no annotations, but with an output schema), the description is reasonably complete. It explains the purpose, return data, and parameters. Since an output schema exists, it doesn't need to detail return values, and the parameter semantics are adequately covered. However, it lacks behavioral context (e.g., safety, limits) and usage guidelines, which are minor gaps.

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 'query' as an optional search/filter query. Since the schema description coverage is 0% (schema provides only titles like 'Project Id' and 'Query'), this adds substantial meaning beyond the schema. However, it doesn't detail the format or syntax of the query parameter, leaving some ambiguity.

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 overview') and resource ('all applications in a project'), and it distinguishes this from sibling tools like 'get_application' (which likely gets details for a single application) by focusing on a high-level view of all applications. However, it doesn't explicitly differentiate from other overview tools like 'get_deployments_overview' or 'get_nodes_overview'.

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 when to choose this over 'get_application' for single-app details or other overview tools like 'get_deployments_overview', nor does it specify prerequisites or exclusions. The only implied usage is for getting an overview, but this is minimal guidance.

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