Skip to main content
Glama

get_photo

Read-only

Retrieve full details for one Apple Photos item by UUID, including metadata, albums, labels, camera, location, and file paths.

Instructions

Full details of one photo: metadata, albums, labels, camera, location and file paths.

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": {
      "uuid": "<uuid>"
    },
    "name": "get_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description correctly stays consistent with a read. The enumeration of returned facets adds useful context about scope of data exposed, but nothing is said about failure behavior for a nonexistent uuid or whether missing fields are omitted or null. With an output schema present, not explaining return shape is acceptable.

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?

A single compact line, front-loaded with the resource and followed by the facets it returns. It is a fragment rather than a grammatical sentence, but no wording is wasted and nothing important is buried.

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?

For a single-parameter read tool with full annotation coverage and an output schema, the definition covers enough to invoke it, but leaves gaps: no call-to-action linking to search_photos to obtain the uuid, and no behavior for unknown identifiers. Adequate but clearly thin for a lookup by opaque identifier.

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?

There is one required parameter with 0% schema description coverage; the schema supplies only the name 'uuid' and no explanation. The description implies a single-identifier lookup but never states that a photo UUID is required or that other identifier forms (path, name) are not accepted, so it only marginally compensates for the coverage 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?

Names the specific resource and scope ('Full details of one photo') and enumerates the returned facets (metadata, albums, labels, camera, location, file paths), which clearly separates it from list-oriented siblings like search_photos or list_albums. It never names an alternative sibling, so differentiation is implicit rather than stated.

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?

Usage is only implied: the phrase 'one photo' signals single-record retrieval rather than bulk listing, so an agent can infer this follows a search step. There is no explicit when-to-use, no prerequisite stated (e.g., obtain the uuid from search_photos first), and no mention of what to do if the identifier is unknown.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.