Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_project_status

Check project health including agent and integration status. Returns overall health, Prometheus connection, node agent deployment, and error messages.

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

  • Implementation handler for get_project_status - calls the client and returns a success/status response.
    @handle_errors
    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 via @mcp.tool() decorator - exposes get_project_status as an MCP tool with docstring describing the parameters and return data.
    @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]
  • Client helper method - makes the actual HTTP GET request to /api/project/{project_id}/status to retrieve project status.
    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?

No annotations are provided, so the description carries the full burden. It implies a read-only operation and lists what status includes, but does not explicitly state side effects, permissions, or rate limitations. Adequate for a simple get tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is reasonably concise but includes an 'Args' section that largely duplicates the schema. Could be streamlined to remove redundancy.

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?

For a simple status tool with one parameter and an output schema, the description adequately lists return fields. However, lacking usage guidance slightly reduces completeness.

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?

The input schema has one parameter with 0% description coverage. The description repeats 'project_id: Project ID' in Args, which adds minimal meaning beyond the schema's title. More detail on format or source would help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves project status including agent and integration health, and lists specific components. It distinguishes itself from sibling tools like 'get_project' or 'health_check' by focusing on status metrics.

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 explicit guidance on when to use this tool versus alternatives such as 'get_project' or 'health_check'. The description only lists output fields without advising on context or prerequisites.

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