Skip to main content
Glama

Decode Interface Builder

decode_interface_builder
Idempotent

Decode compiled storyboard and nib archives in an active Apple app bundle into bounded object, hierarchy, and connection graphs for static interface analysis.

Instructions

Decode compiled storyboard and nib archives inside the active Apple app bundle, including keyed property lists and NIBArchive object tables, into a bounded object, hierarchy, and connection graph. This is static archive parsing; unrecognized archive classes and unresolved code handlers remain explicit unknowns.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "decode_interface_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_objectsNoMaximum permitted objects for this operation.
max_documentsNoMaximum permitted documents for this operation.
max_connectionsNoMaximum permitted connections for this operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare safety hints (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description adds real value: it discloses that parsing is static, that output is bounded, and that unrecognized archive classes and unresolved code handlers are returned as explicit unknowns rather than errors. It does not explain why the tool is flagged non-read-only, which leaves a small gap for a parse operation.

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, both front-loaded and free of filler: the first gives action, scope, and output shape; the second gives parser semantics and failure handling. Dense but every clause contributes information.

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?

With no output schema, the description does describe the return shape (object, hierarchy, and connection graph) and the handling of unresolvable items. Remaining gaps — such as whether the active app bundle must be selected first and what output format the graph uses — are modest for a three-optional-parameter read tool.

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% and every parameter (max_objects, max_connections, max_documents) is documented in the schema, so the schema carries the burden. The description references boundedness generally, which loosely ties to those limits, but adds no per-parameter meaning such as defaults or truncation behavior.

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?

States a specific verb and resource — decoding compiled storyboard and nib archives inside the active Apple app bundle — and names the artifact subtypes (keyed property lists, NIBArchive object tables). It is clearly distinguishable from siblings like decode_android_resources or inspect_evm_interface on platform and artifact type.

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 'inside the active Apple app bundle' implies an active session/app context prerequisite, and 'static archive parsing' implies the when-to-use case of inspecting resources without executing code. However, it never explicitly says when to choose this over alternatives, nor does it state preconditions or exclusions directly.

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