Skip to main content
Glama

osxphotos_help

Read-only

Displays help for a specified osxphotos command or lists available commands, optionally filtering options by topic to find relevant usage details.

Instructions

Help for one osxphotos command, or the list of available commands if none is given.

Pass a topic (one word, for example "location") to see only the options about it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
topicNo
commandNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 bar is lower. The description usefully discloses the no-argument fallback behavior (returns the command list), but says nothing about output shape or error behavior for unknown input.

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?

Very short and front-loaded: the main behavior comes first, then the topic refinement. Slightly awkward phrasing ('Pass a topic ... to see only the options about it') but no wasted sentences.

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?

An output schema exists so return values need not be explained, and readOnly annotations cover safety. However, with two optional params and zero schema descriptions, the command parameter's semantics (full command name? subcommand?) remain unstated.

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 description coverage is 0%, so the description carries the burden: it explains the topic parameter concretely (one word, e.g. "location") and filters options, which the bare schema does not. The command parameter is only implied by 'Help for one osxphotos command' rather than documented explicitly, keeping it below 5.

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?

States a specific resource and behavior: help for a single osxphotos command, or the command list when no command is supplied. That distinguishes it from action-oriented siblings like run_osxphotos and export_photos, though it never names those siblings explicitly.

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?

Gives a conditional rule ('or the list of available commands if none is given') and a filtering rule for topic, which implies how to call it. It does not say when to prefer this over run_osxphotos, nor what happens if an unknown command/topic is passed.

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