Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_project

Retrieve project details and configuration from Coroot observability platform to access settings, integrations, and monitoring setup.

Instructions

Get project details and configuration.

Retrieves comprehensive information about a project including its settings, integrations, and configuration.

Args: project_id: Project ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_project'. Decorated with @mcp.tool() for registration and executes by calling the implementation helper which invokes CorootClient.get_project()
    @mcp.tool()
    async def get_project(project_id: str) -> dict[str, Any]:
        """Get project details and configuration.
    
        Retrieves comprehensive information about a project including
        its settings, integrations, and configuration.
    
        Args:
            project_id: Project ID
        """
        return await get_project_impl(project_id)  # type: ignore[no-any-return]
  • Helper implementation for get_project tool that wraps CorootClient.get_project() call and formats the response
    async def get_project_impl(project_id: str) -> dict[str, Any]:
        """Get project details."""
        project = await get_client().get_project(project_id)
        return {
            "success": True,
            "project": project,
        }
  • CorootClient method that performs the actual HTTP GET request to retrieve project details from /api/project/{project_id}
    async def get_project(self, project_id: str) -> dict[str, Any]:
        """Get project details.
    
        Args:
            project_id: Project ID.
    
        Returns:
            Project configuration dictionary.
        """
        response = await self._request("GET", f"/api/project/{project_id}")
        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. It states the tool retrieves information (implying read-only), but doesn't disclose behavioral traits such as required permissions, rate limits, error conditions, or whether it returns real-time or cached data. The description adds minimal value beyond the implied read operation, leaving key behavioral aspects unspecified.

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, starting with a clear purpose statement followed by elaboration and parameter details. Every sentence adds value without redundancy, and it's appropriately sized for a simple retrieval tool. No wasted words or unnecessary complexity.

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 low complexity (single parameter, read operation) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose and parameter semantics adequately. However, it lacks behavioral details (e.g., permissions, errors) that would be beneficial despite the output schema, keeping it from a perfect score.

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 adds meaningful context for the single parameter 'project_id' by specifying it as 'Project ID', which clarifies its purpose beyond the schema's generic 'Project Id' title. With 0% schema description coverage and only one parameter, the description effectively compensates by providing essential semantic information, though it could elaborate on format or sourcing.

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', 'Retrieves') and identifies the resource ('project details and configuration', 'comprehensive information about a project'). It distinguishes from obvious siblings like 'list_projects' (which lists multiple) and 'get_project_status' (which focuses on status rather than comprehensive details), though it doesn't explicitly name alternatives. The purpose is specific but could be more precise about what 'comprehensive' entails.

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 siblings like 'get_project_status' for status-only queries or 'list_projects' for listing multiple projects, nor does it specify prerequisites or contexts (e.g., after creating a project). Usage is implied by the purpose but lacks explicit direction.

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