Skip to main content
Glama

Inspect Plist

inspect_plist
Idempotent

Parse Info.plist from the active artifact or a local path and return normalized JSON instead of raw plutil text.

Instructions

Parse Info.plist from the active artifact by default, or pass any local plist path. Returns normalized JSON rather than plutil text.

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": {
      "path": "/Applications/Example.app/Contents/Info.plist"
    },
    "name": "inspect_plist"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoLocal filesystem path used by this operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is largely pre-supplied. The description adds genuinely new behavioral context by specifying the return form (normalized JSON, not plutil text), but says nothing about failure behavior on malformed or binary plists, and its purely read-like framing sits slightly awkwardly with readOnlyHint=false. That is a mild tension rather than a contradiction.

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, no filler, with the default behavior front-loaded before the override and the output guarantee. Every clause carries information an agent needs to make the call.

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 one-parameter, annotation-covered tool with no output schema, the definition covers default scope, override scope, and return format, which is nearly everything needed. The only gap is error/edge-case behavior for invalid or non-XML plists, which is a minor omission.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description earns more: the schema only says "Local filesystem path used by this operation," while the definition clarifies that the path is optional and that omitting it resolves to the active artifact's Info.plist. That is real semantic value 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?

States a specific verb and resource ("Parse Info.plist"), names the scope ("from the active artifact by default"), and contrasts the output with the plutil text alternative. An agent can tell immediately what this tool produces and how it differs from a generic artifact inspector.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear selection guidance for its one optional parameter: omit path to parse the active artifact's Info.plist, or supply a local plist path to target something else. It doesn't state when-not to use it or name an alternative tool, but for a single-parameter parser the default/override rule covers the realistic decision.

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