Skip to main content
Glama
Sign In
podium-mcp

podium-mcp

by hoainho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_list

Retrieves installed apps on a booted iOS simulator, returning bundle ID, display name, and application type (User/System) for a given simulator UDID.

Instructions

Returns the list of installed apps on a booted iOS simulator. Includes bundle ID, display name, and application type (User/System).

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>"
    },
    "name": "app_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
udidYesSimulator UDID (from device_list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist. The description indicates a read-only operation and states the required condition (booted simulator). However, it doesn't disclose error handling or behavior when the simulator is not booted.

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?

Two sentences with no wasted words. Front-loaded with the core action and includes key details.

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 low-complexity tool with one parameter and no output schema, the description adequately covers the return fields and precondition (booted simulator). Could mention error scenarios but overall sufficient.

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?

The input schema has 100% coverage for the single parameter 'udid' with a description. The tool's description does not add additional meaning beyond the 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 'Returns the list of installed apps on a booted iOS simulator' with specific fields. This distinguishes it from sibling tools like app_install, app_launch, 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?

No explicit when-to-use or alternatives guidance is provided. The usage is implied by the tool's purpose, but it doesn't mention when to choose app_list over other listing tools.

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