Photo Shoot Planner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_locationA | Geocode a place name to candidate coordinates using OpenStreetMap Nominatim. |
| get_astronomyA | Compute moon phase/rise/set, golden hour, blue hour, and astronomical darkness for coordinates and an ISO date/time. |
| get_sky_timelineB | Sample sun/moon positions through a shoot window; useful for moon alignment and Milky Way darkness planning. |
| get_weatherA | Fetch hourly cloud cover, visibility, precipitation, wind and temperature from Open-Meteo for a shoot window. |
| assess_dark_skyB | Interpret a supplied Bortle class or sky-quality reading. Does not invent a site rating. |
| compare_viewpointsC | Rank candidate viewpoints using darkness, horizon, access, and foreground scores. |
| plan_routeB | Estimate driving route, distance and duration between coordinates using the public OSRM service. |
| find_nearby_lodgingC | Find nearby mapped hotels/motels/hostels via OpenStreetMap Overpass; verify availability and breakfast directly. |
| recommend_camera_settingsA | Generate conservative starting settings for a camera/lens and subject; photographer must meter and adjust on site. |
| calculate_shoot_budgetC | Calculate estimated, committed, and actual photoshoot costs with tax, contingency, category totals, and variances. |
| build_call_sheetA | Validate schedule math and produce a structured call sheet with overlaps, gaps, and total production-day duration. |
| generate_release_checklistA | Generate a case-specific issue-spotting checklist for permits, releases, insurance, and usage rights. This is not legal advice. |
| validate_shoot_readinessB | Score production readiness and separate critical blockers from warnings and completed checks. |
| create_shooting_planB | Turn verified inputs into a printable Markdown field plan. Pass only facts already gathered; unknowns remain explicit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_photo_trip | Plan a complete photography trip with evidence and a field-ready handoff. |
| compare_photo_locations | Compare candidate photo locations for a date and subject. |
| plan_photo_production | Build a complete professional photoshoot production book. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct concern (astronomy, location, weather, route, budget, checklists), so most boundaries are clear. get_astronomy and get_sky_timeline have some overlap in sky computation, but get_astronomy focuses on a single instant while get_sky_timeline samples a window, which descriptions clarify.
Tools follow a consistent verb_noun pattern (get_, assess_, compare_, plan_, find_, recommend_, calculate_, build_, generate_, validate_, create_). The verbs are varied but predictable; the only minor inconsistency is that some verbs (get_) are fetch-based while others (validate_, create_) are generative, but the pattern holds throughout.
14 tools is well within the ideal 3-15 range and each tool maps to a distinct production phase: site selection, astronomy, weather, logistics, budget, call sheet, and planning deliverable. Every tool appears necessary to the stated photoshoot planning workflow.
The surface covers the full lifecycle from location/astronomy/weather discovery through route/lodging logistics, cost/budget, and production deliverables (call sheet, releases, readiness score, and field plan). No obvious dead ends; the suite forms a coherent planning pipeline from ideation to execution.