Skip to main content
Glama

get_app

Retrieve details of a specific application using its unique ID. Provide the app ID to access build status, configuration, and metadata.

Instructions

Get details of a specific application by its ID.

Args: app_id: The Codemagic application ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes

Implementation Reference

  • The MCP tool handler for 'get_app' - registers the tool with FastMCP, accepts an app_id, and delegates to the client layer.
    @mcp.tool()
    async def get_app(app_id: str) -> Any:
        """Get details of a specific application by its ID.
    
        Args:
            app_id: The Codemagic application ID.
        """
        async with CodemagicClient() as client:
            return await client.get_app(app_id)
  • The API client method that performs the actual HTTP GET request to /apps/{app_id}, extracts the application data, and trims it via _trim_app.
    async def get_app(self, app_id: str) -> Any:
        data = await self._get(f"/apps/{app_id}")
        app = data.get("application", data) if isinstance(data, dict) else data
        return self._trim_app(app)
  • Registration entry point - calls apps.register(mcp) which registers the get_app tool along with other app tools.
    def register_all_tools(mcp: FastMCP) -> None:
        apps.register(mcp)
        builds.register(mcp)
  • Server initialization - creates the FastMCP instance and calls register_all_tools to register all tools including get_app.
    mcp = FastMCP(
        name="Codemagic MCP",
        instructions=(
            "Codemagic CI/CD REST API: manage builds, apps, artifacts, caches, variables, and webhooks.\n\n"
            "Destructive ops (delete_app, cancel_build, delete_cache, delete_all_caches, delete_variable, delete_webhook): confirm before executing.\n\n"
            "App ID resolution: (1) use explicit app_id; (2) use CODEMAGIC_DEFAULT_APP_ID if set (exposed as `default_app_id`); "
            "(3) call list_apps — auto-select if one result, else ask user."
        ),
        lifespan=lifespan,
    )
    
    register_all_tools(mcp)
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It states 'Get details' (read operation) but doesn't confirm idempotency, error handling (e.g., invalid ID), or permission requirements. Minimal transparency beyond the basic verb.

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 extremely concise: a single sentence defining the purpose plus an Args line for the parameter. Every word adds value, with no redundant repetition of the tool name or schema.

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 retrieval tool with one parameter and no output schema, the description covers the core purpose and parameter meaning. It lacks details about the response structure, but the context of sibling tools and the tool name compensate somewhat.

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 explains the lone parameter 'app_id' as 'the Codemagic application ID', adding meaning beyond the schema's title and type. With 0% schema coverage, this is valuable context. However, it doesn't specify format or examples.

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 retrieves details of a specific application by ID. The verb 'Get' and resource 'application' are specific and distinct from sibling tools like list_apps or delete_app. However, it doesn't define what 'details' includes.

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 use when you need details of a known app, but provides no explicit guidance on when to use alternatives (e.g., list_apps) or prerequisites like authentication. Adequate for a simple retrieval but lacks context for complex decisions.

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/AgiMaulana/CodemagicMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server