Skip to main content
Glama
Sign In
Karagöz

Karagöz

by yagizdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Install an app

install
Destructive

Deploy an .apk, .app, or .ipa to an Android device, iOS simulator, or iPhone, replacing the existing app version when needed.

Instructions

Install an .apk, or a .app or .ipa on an iOS simulator or iPhone, or replace the installed version of the same app. An iPhone takes only a build signed for it; karagoz does not re-sign. Times out after 30 s plus 1 s per MB.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "apk": "<apk>"
    },
    "name": "install"
  }
}

Input Schema

NameRequiredDescriptionDefault
apkYesAbsolute path to the .apk, .app or .ipa.
deviceNoId or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the overwrite behaviour, the no-re-signing constraint, and the timeout formula (30 s + 1 s per MB), which an agent cannot infer from structured fields. However it says nothing about failure/return signalling after a failed install.

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?

Two dense sentences with no filler, leading with the primary action and artifact types. The middle clause ('a .app or .ipa on an iOS simulator or iPhone') is slightly tangled but still parses.

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 two-parameter tool with no output schema, it covers the essentials an agent needs: accepted formats, overwrite semantics, signing prerequisite, and timeout budget. The main missing piece is guidance on the install_runner sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, making 3 the baseline. The description restates the accepted file extensions but adds no meaning beyond the schema and never explains the device parameter (id vs name).

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?

States a specific verb (install) plus the accepted artifact types (.apk, .app, .ipa) and the replacement behaviour. It does not distinguish itself from the sibling install_runner, so an agent cannot tell which of the two install paths to pick from the description alone.

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

Usage Guidelines4/5

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

Gives concrete conditions: use for .apk/.app/.ipa on a simulator or iPhone, and it will replace the same app if already present. It also flags the prerequisite that an iPhone only accepts a build signed for it. It stops short of naming the alternative (install_runner) or the when-not case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools