Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get AllTrails trail

alltrails_get_trail
Read-onlyIdempotent

Fetch a single AllTrails trail by numeric ID to get name, location, length, elevation gain, difficulty, rating, and route type; request full view or offline detail for geometry.

Instructions

Get details for a single AllTrails trail by its numeric trail id. Returns name, location, length, elevation gain, difficulty, rating, route type, and (at higher detail levels) route geometry. Returns a slim projection by default (name, overview, length in m+mi, elevation gain, difficulty, rating, route type, location); pass view:"full" for the whole record and geometry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns { name, overview, length in m+mi, elevation gain in m+ft, difficulty, rating, route type, location }, unwrapped from the one-element envelope; "full" returns the whole record, route geometry included (which also needs detail:"offline" to be fetched at all).
detailNoDetail level. "medium" (default) is a good overview; "offline" includes full route geometry.
trailIdYesNumeric AllTrails trail id (e.g. "10236086")

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 instead of the full record (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 { name, overview, length in m+mi, elevation gain in m+ft, difficulty, rating, route type, location }, unwrapped from the one-element envelope; \"full\" returns the whole record, route geometry included (which also needs detail:\"offline\" to be fetched at all).",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description goes beyond them by disclosing that the response is a slim projection by default, what exactly that projection contains, and that route geometry is only fetched when both view:"full" and detail:"offline" are set — a genuinely useful behavioral detail. It does not cover error behavior for invalid ids.

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 verb and resource, and appropriately sized. There is minor redundancy: the field list appears twice (once as the general return set, once again as the compact projection), which costs a few words without adding information.

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?

There is no output schema, but the description compensates by naming the returned fields and explaining the compact/full shapes and the geometry dependency, which is enough for an agent to call and interpret this read-only tool. Missing only edge-case behavior (invalid or unknown trail ids).

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 description coverage is 100%, so the schema already documents trailId, view and detail in detail. The description largely restates the default projection and the view:"full" behavior that the view parameter's own schema text already specifies, adding only a mild emphasis on the view+detail interaction for geometry. Baseline 3 is appropriate.

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 ("Get details for a single AllTrails trail by its numeric trail id") and enumerates the returned field set, which cleanly separates it from siblings like alltrails_get_trail_gpx, alltrails_get_trail_reviews, alltrails_get_trail_photos and alltrails_get_trail_weather. An agent can identify this as the canonical trail-detail call without opening any other schema.

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?

The description explains when to choose view:"full" over the default projection, which is useful parameter-level guidance, but it never states when to call this tool instead of, or in addition to, its many siblings, nor any prerequisites (e.g. resolving a trail id first via alltrails_search). Usage is implied by the tool name rather than stated.

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