Skip to main content
Glama
Sign In
podium-mcp

podium-mcp

by hoainho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_install

Install an app on an iOS simulator by providing the path to a .app directory or .zip archive. Specify the simulator UDID to target the correct device.

Instructions

Installs an app on an iOS simulator. Accepts a path to a .app directory or a .zip archive.

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": {
      "udid": "<udid>",
      "path": "<path>"
    },
    "name": "app_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
udidYesSimulator UDID
pathYesPath to the .app directory or .zip file to install

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations, so description carries full burden. It states installation but does not disclose whether it overwrites, checks for existing app, requires simulator booted, or handles errors.

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?

Single sentence, no wasted words, front-loaded with the essential purpose.

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 simple tool, but lacks info on prerequisites, side effects, or success criteria, leaving gaps for an AI agent.

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 coverage is 100% with clear parameter descriptions. Description adds no new meaning beyond stating accepted formats, which is already covered in the path parameter description.

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?

Description clearly states it installs an app on an iOS simulator and specifies accepted formats (.app or .zip), distinguishing it from sibling tools like app_launch, app_list, etc.

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?

Implies usage for installing apps, but no explicit guidance on when to use versus alternatives, prerequisites, or when not to use.

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