Skip to main content
Glama

get_app

Retrieve application details by ID from Codemagic CI/CD to manage builds, artifacts, and configurations directly within Claude.

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 'get_app' tool handler, which calls the CodemagicClient to retrieve application details.
    @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 actual API implementation for 'get_app' in the CodemagicClient.
    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)
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but only states it retrieves details. It omits behavioral specifics: what happens if the ID is invalid, what fields are returned (no output schema exists), whether this is a cached or live lookup, or permission requirements.

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 content is not verbose, but the 'Args:' docstring-style formatting is unconventional for MCP descriptions and slightly disjointed from the opening sentence. No redundant phrases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a single-parameter retrieval tool, but minimal. With no output schema and no annotations, the description should ideally preview what 'details' are returned or link to documentation. Currently停在 viable but incomplete.

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?

Schema description coverage is 0% (app_id only has title/type). The description compensates via the 'Args:' section explaining 'app_id: The Codemagic application ID', which adds crucial domain context ('Codemagic') absent from the schema. However, it doesn't describe the ID format or constraints.

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 action ('Get details'), resource ('application'), and identification method ('by its ID'), distinguishing it from list_apps (plural) and mutation siblings like add_app/delete_app. However, it lacks the 'Codemagic' context found in the Args section, which would further clarify domain specificity.

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 guidance provided on when to use this versus list_apps (e.g., 'use when you already know the app ID' vs 'use list_apps to discover IDs'). No prerequisites or error conditions 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/AgiMaulana/CodemagicMcp'

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