Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get AllTrails trail photos

alltrails_get_trail_photos
Read-onlyIdempotent

Retrieve photos for an AllTrails trail using its numeric trail ID, returning image URLs and metadata; use full view for complete photo records.

Instructions

Get photos for an AllTrails trail by its numeric trail id. Returns just { id, title, likeCount, user, uploadedAt, url } per photo by default — the url serves the actual image; pass view:"full" for the whole records.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns { count, photos: [{ id, title, likeCount, user, uploadedAt, url }] } — the url is DERIVED and signed here, so "full" (AllTrails' whole photo records) does not contain it. No route geometry either way — that is alltrails_get_trail.
trailIdYesNumeric AllTrails trail id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.9
    • addedInput schema / properties / trailId / pattern
      Added value: +"^\\d+$"
  2. Changed1 schema field changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Return a slim projection per photo (default false)",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns { count, photos: [{ id, title, likeCount, user, uploadedAt, url }] } — the url is DERIVED and signed here, so \"full\" (AllTrails' whole photo records) does not contain it. No route geometry either way — that is alltrails_get_trail.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description still adds real behavior: the default shape is trimmed, and the 'url' is a derived/signed field that 'full' records do not contain. It stops short of stating auth needs or rate limits, but the response-shape nuance is valuable.

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 core action and identifier, then the response-shape caveat. No filler, though the second sentence is slightly run-on and mixes return format with parameter guidance.

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 carries the return-value burden and does so by naming the per-photo fields returned by default. It omits pagination or the enclosing count structure that the schema mentions, but an agent has enough to call and interpret the result.

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 coverage is 100% and the enum is already documented in the schema, so baseline is 3. The description does clarify that 'url' serves the actual image and that 'full' returns whole records, but this largely restates what the schema's view description already says.

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 verb and resource ('Get photos for an AllTrails trail') plus the identifier needed ('by its numeric trail id'). The resource is unambiguous against siblings like alltrails_get_trail_reviews or alltrails_get_trail_weather, but the description itself never names an alternative to route the agent.

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?

Implies usage by describing the default response and when to switch to view:"full", but gives no when-to-use / when-not-to-use framing or pointer to sibling tools for adjacent data (reviews, gpx, weather). The agent must infer context from the tool name.

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