Skip to main content
Glama

Inspect Asset Catalog

inspect_asset_catalog
Idempotent

Inspect compiled Assets.car metadata in an active Apple app bundle to retrieve paginated catalog and rendition records with assetutil details and digests; does not extract rendition bytes.

Instructions

Inspect compiled Assets.car metadata in an active Apple app bundle. Returns stable paginated catalog and rendition records with raw assetutil metadata and catalog digests; rendition bytes are not extracted.

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": {
      "limit": 1000,
      "offset": 0
    },
    "name": "inspect_asset_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the return shape (stable paginated catalog and rendition records, raw assetutil metadata, catalog digests) and an explicit scope limit that rendition bytes are not extracted. What it does not cover is the odd readOnlyHint=false posture: the wording describes a purely observational operation, so an agent gets no explanation of why the tool is marked as non-read-only or whether it touches disk state.

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 resource and scope, then the return contract and the exclusion. The exclusion clause is genuinely load-bearing, but 'raw assetutil metadata' and 'catalog digests' are dense jargon that assumes the reader already knows the assetutil toolchain.

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 the necessary work of describing return values and explicitly excluding rendition bytes, which is the most likely wrong expectation for an agent. The remaining gaps are pagination mechanics and the mismatch between the observational framing and readOnlyHint=false, neither of which would cause a failed invocation.

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 0%, so all meaning for the limit and offset parameters must come from the description, which only signals 'stable paginated' without documenting defaults (1000/0), the 1-10000 limit cap, or what 'stable' ordering guarantees. The pagination hint does connect to both parameters, so this is partial compensation rather than none.

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 names a concrete verb and resource: inspecting compiled Assets.car metadata inside an active Apple app bundle, and it states what is returned (catalog and rendition records). That is enough to separate it from generic archive or binary tools, but it never names an adjacent sibling or states a boundary case where another inspector would be correct.

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 'in an active Apple app bundle' implies a precondition (the asset catalog must already be compiled and reachable in a live bundle), and 'rendition bytes are not extracted' implies a negative boundary. There is no explicit when-to-use statement, no alternative tool named, and no guidance on choosing between this and other artifact inspectors.

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