Skip to main content
Glama
jamesbrink

MCP Server for Coroot

get_inspection_config

Retrieve configuration for application performance inspections like CPU, memory, or SLO monitoring to analyze and manage observability settings.

Instructions

Get inspection configuration for an application.

Retrieves the current configuration for a specific inspection type (e.g., cpu, memory, slo_availability, slo_latency) for an application.

Args: project_id: Project ID app_id: Application ID (format: namespace/kind/name) inspection_type: Type of inspection (cpu, memory, slo, etc)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
app_idYes
inspection_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function that executes the get_inspection_config tool by calling the internal implementation.
    @mcp.tool()
    async def get_inspection_config(
        project_id: str,
        app_id: str,
        inspection_type: str,
    ) -> dict[str, Any]:
        """Get inspection configuration for an application.
    
        Retrieves the current configuration for a specific inspection type
        (e.g., cpu, memory, slo_availability, slo_latency) for an application.
    
        Args:
            project_id: Project ID
            app_id: Application ID (format: namespace/kind/name)
            inspection_type: Type of inspection (cpu, memory, slo, etc)
        """
        return await get_inspection_config_impl(  # type: ignore[no-any-return]
            project_id, app_id, inspection_type
        )
  • Internal implementation of the tool handler that uses the CorootClient to fetch the inspection configuration.
    @handle_errors
    async def get_inspection_config_impl(
        project_id: str,
        app_id: str,
        inspection_type: str,
    ) -> dict[str, Any]:
        """Get inspection configuration."""
        config = await get_client().get_inspection_config(
            project_id, app_id, inspection_type
        )
        return {
            "success": True,
            "config": config,
        }
  • FastMCP tool registration decorator for the get_inspection_config tool.
    @mcp.tool()
  • CorootClient helper method that makes the actual API request to retrieve the inspection configuration.
    async def get_inspection_config(
        self, project_id: str, app_id: str, inspection_type: str
    ) -> dict[str, Any]:
        """Get inspection configuration for an application.
    
        Args:
            project_id: Project ID.
            app_id: Application ID.
            inspection_type: Type of inspection (cpu, memory, slo, etc).
    
        Returns:
            Inspection configuration.
        """
        # URL encode the app_id since it contains slashes
        from urllib.parse import quote
    
        encoded_app_id = quote(app_id, safe="")
    
        response = await self._request(
            "GET",
            f"/api/project/{project_id}/app/{encoded_app_id}/inspection/{inspection_type}/config",
        )
        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 full burden. It clearly indicates this is a read operation ('Get', 'Retrieves'), which is helpful. However, it doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether the configuration data is cached/live. The description adds basic context but lacks operational details.

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 efficiently structured: a clear purpose statement, followed by a slightly more detailed explanation, then parameter documentation. Every sentence adds value with no redundancy. The Args section is well-organized and directly useful.

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), 3 parameters with good semantic coverage in the description, and no annotations, the description is reasonably complete. It explains what the tool does, what parameters mean, and the retrieval nature. For a read operation with output schema, only minor gaps remain (like authentication or error handling).

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, the description compensates well by explaining all three parameters in the Args section: project_id (Project ID), app_id (Application ID with format: namespace/kind/name), and inspection_type (Type of inspection with examples: cpu, memory, slo, etc). This adds meaningful context beyond the bare schema.

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 specific action ('Get inspection configuration for an application') and resource ('inspection configuration'), with explicit examples of inspection types (cpu, memory, slo_availability, slo_latency). It distinguishes from sibling tools like 'list_inspections' (which likely lists all inspections) and 'update_inspection_config' (which modifies configuration).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying it retrieves configuration 'for an application' and 'for a specific inspection type', but doesn't explicitly state when to use this tool versus alternatives like 'list_inspections' or 'get_application' (which might provide different data). No explicit exclusions or prerequisites are mentioned.

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