Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_nodes_overview

Retrieve an overview of infrastructure nodes, including health status, resource utilization, running containers, and system metrics, with optional search/filter by query.

Instructions

Get overview of infrastructure nodes.

Returns information about all nodes in the infrastructure:

  • Node health and status

  • Resource utilization

  • Running containers

  • System metrics

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

  • MCP tool registration via @mcp.tool() decorator for get_nodes_overview
    @mcp.tool()
    async def get_nodes_overview(
        project_id: str,
        query: str | None = None,
    ) -> dict[str, Any]:
        """Get overview of infrastructure nodes.
    
        Returns information about all nodes in the infrastructure:
        - Node health and status
        - Resource utilization
        - Running containers
        - System metrics
    
        Args:
            project_id: Project ID
            query: Search/filter query (optional)
        """
        return await get_nodes_overview_impl(project_id, query)  # type: ignore[no-any-return]
  • Handler function that calls client to get nodes overview data
    @handle_errors
    async def get_nodes_overview_impl(
        project_id: str,
        query: str | None = None,
    ) -> dict[str, Any]:
        """Get nodes overview."""
        overview = await get_client().get_nodes_overview(project_id, query)
        return {
            "success": True,
            "overview": overview,
        }
  • CorootClient method that makes the actual HTTP GET request to /api/project/{project_id}/overview/nodes
    async def get_nodes_overview(
        self,
        project_id: str,
        query: str | None = None,
    ) -> dict[str, Any]:
        """Get infrastructure nodes overview.
    
        Args:
            project_id: Project ID.
            query: Search/filter query.
    
        Returns:
            Nodes overview data.
        """
        params = {}
        if query:
            params["query"] = query
    
        response = await self._request(
            "GET",
            f"/api/project/{project_id}/overview/nodes",
            params=params,
        )
        data: dict[str, Any] = response.json()
        return data
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It lists returned information types (health, status, etc.) but does not explicitly state read-only nature or any side effects, permissions, or rate limits. Adequate but not fully transparent.

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?

Concise with clear front-loaded purpose, bullet points for returned info, and explicit parameter list. No wasted words.

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 no annotations and moderate complexity, description covers purpose and output fields moderately, but lacks usage context, parameter constraints, or any behavioral details beyond basic info.

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?

Schema description coverage is 0%, so description must compensate. It lists two arguments with minimal explanation (project_id as 'Project ID', query as 'Search/filter query (optional)'). Adds little beyond schema field names and types.

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?

Description clearly states verb (Get overview) and resource (infrastructure nodes) with specific details (health, status, resource utilization, etc.). Does not explicitly differentiate from sibling tool 'get_node', but name implies all nodes vs single node.

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 on when to use this tool vs alternatives like 'get_node' or other overview tools. Does not mention prerequisites or exclusions.

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