Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_project_status

Retrieve project health status, including agent deployment, Prometheus connections, and error details for monitoring infrastructure performance.

Instructions

Get project status including agent and integration health.

Returns the current status of a project including:

  • Overall project health

  • Prometheus connection status

  • Node agent deployment status

  • Any error messages

Args: project_id: Project ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation that fetches project status via CorootClient and wraps in success response.
    async def get_project_status_impl(project_id: str) -> dict[str, Any]:
        """Get project status."""
        status = await get_client().get_project_status(project_id)
        return {
            "success": True,
            "status": status,
        }
  • MCP tool registration using @mcp.tool() decorator with input schema from signature and docstring.
    @mcp.tool()
    async def get_project_status(project_id: str) -> dict[str, Any]:
        """Get project status including agent and integration health.
    
        Returns the current status of a project including:
        - Overall project health
        - Prometheus connection status
        - Node agent deployment status
        - Any error messages
    
        Args:
            project_id: Project ID
        """
        return await get_project_status_impl(project_id)  # type: ignore[no-any-return]
  • CorootClient helper method that performs the actual HTTP request to retrieve project status from Coroot API.
    async def get_project_status(self, project_id: str) -> dict[str, Any]:
        """Get project status including Prometheus and agent status.
    
        Args:
            project_id: Project ID.
    
        Returns:
            Project status dictionary.
        """
        response = await self._request("GET", f"/api/project/{project_id}/status")
        data: dict[str, Any] = response.json()
        return data
Behavior3/5

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

With no annotations provided, the description carries the full burden. It describes what information is returned (health metrics, connection statuses, error messages) which is useful behavioral context. However, it doesn't mention important operational aspects like whether this requires special permissions, rate limits, or how frequently the status updates.

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 with a clear purpose statement followed by a bulleted list of returned information and a parameter explanation. It's appropriately sized for a single-parameter tool, though the 'Args:' section could be integrated more smoothly with the main description.

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 has an output schema (which handles return values) and only one parameter, the description provides good context about what status information is returned. For a read-only status-checking tool with output schema support, this description is reasonably complete, though it could benefit from more operational context.

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?

With 0% schema description coverage and only one parameter, the description provides essential context by explaining that 'project_id' identifies which project's status to retrieve. This adds meaningful semantics beyond the bare schema, though it doesn't specify format constraints or validation rules.

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 specific verbs ('Get project status') and resources ('project'), and lists the specific health components returned. However, it doesn't explicitly distinguish this from sibling tools like 'get_project' or 'get_nodes_overview' which might provide overlapping information.

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. With many sibling tools like 'get_project', 'get_nodes_overview', and 'health_check', there's no indication of when this specific status-checking tool is appropriate versus other monitoring or project information tools.

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