Skip to main content
Glama

Project Apple Application Graph

project_apple_application_graph
Idempotent

Projects authenticated IPA, .app, ZIP, or DMG Evidence into an execution-free Apple app inventory of roots, nested bundles, launchd plists, hashes, runtime hints, and bridge hypotheses.

Instructions

Project authenticated IPA, macOS .app directory, ZIP, or DMG inventory Evidence into an execution-free Apple application inventory. Reports application roots, nested bundles with path-convention roles (app extensions, XPC services, login items, privileged helpers, system extensions, frameworks), launchd plists, exact component paths and hashes, runtime-family hints, and path-based bridge hypotheses without parsing plist/CMS semantics or claiming observed runtime calls.

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": {
      "inventory_evidence": "<inventory_evidence>"
    },
    "name": "project_apple_application_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
inventory_evidenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=false, idempotentHint=true and destructiveHint=false, so safety basics are covered; the description adds real value beyond that by framing the operation as 'execution-free' and disclaiming semantic parsing and runtime claims, telling the agent exactly how far to trust the output. It does not explain why readOnlyHint=false despite the read-like framing, leaving a minor gap.

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 sentences, front-loaded with the action and artifact inputs, then the reported outputs. It is dense but every clause carries information; the long enumeration of bundle roles is justified because it tells the agent what the inventory will contain.

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?

With no output schema, the description helpfully enumerates the produced data (roots, nested bundles, launchd plists, paths and hashes, bridge hypotheses), which is good compensation. But for a tool whose only input is a large structured Evidence array, the absence of any guidance on assembling that input leaves a significant completeness gap.

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

Parameters2/5

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

There is a single required parameter, inventory_evidence, whose deeply nested Evidence schema has 0% description coverage and many required fields (evidence_id pattern, subject, provider, authority, locations, etc.). The description only gestures at 'authenticated ... Evidence' and never explains how to construct or validate a record, so it fails to compensate for the schema gap.

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 opens with a specific verb and resource — 'Project ... Evidence into an execution-free Apple application inventory' — and immediately scopes it by accepted artifact types (IPA, macOS .app directory, ZIP, DMG), which naturally separates it from the android/harmony/managed projection siblings. It stops short of naming an alternative explicitly, but the Apple-format scoping makes the target unambiguous.

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 phrase 'authenticated ... Evidence' implies a prerequisite, and the closing clause states what the tool does NOT do (no plist/CMS parsing, no observed runtime calls), which is a useful exclusion. However, there is no explicit statement of when to pick this tool over project_android_application_graph or compare_application_versions, so the agent must infer the routing.

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