Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

alltrails_search

Read-only

Search AllTrails by name or keywords to locate trails, points of interest, areas, and cities; optionally filter results to trails only.

Instructions

Search AllTrails by name. A free-text query goes to the suggestions endpoint the alltrails.com search box itself uses — relevance is good and the limit is honored. Results may mix record types (trail, poi, area, city, …); pass types=["trail"] to narrow. lat/lng are accepted for backward compatibility but verified ignored by the API (2026-07-02) — results carry an implicit account/IP geo bias instead. Without a query this falls back to the legacy explore search, which returns trails anchored to the signed-in account's location. Results come back as slim per-result summaries, capped at limit client-side, by default; pass view:"full" for AllTrails' whole records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoDeprecated — the API ignores it (verified 2026-07-02)
lngNoDeprecated — the API ignores it (verified 2026-07-02)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns slim per-result summaries capped at limit; "full" returns AllTrails' whole records.
limitNoMax results to return (default 20)
queryNoFree-text search, e.g. "angels landing" or "waterfall trails"
typesNoRecord types to return (default: all). e.g. ["trail"] for trails only. Only applied when query is provided; silently ignored on the no-query legacy browse fallback.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Return slim per-result summaries capped at limit instead of the full records (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 slim per-result summaries capped at limit; \"full\" returns AllTrails' whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the behavioral burden and fully delivers. It discloses that lat/lng are ignored, geo-bias applies, the fallback behavior depends on signed-in account, and that results are capped client-side by default — all non-obvious behaviors the agent could not infer from schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and each subsequent sentence earns its place by explaining a distinct behavioral nuance. Though it is detailed, it remains tightly organized with no redundant fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with no output schema and six optional parameters, the description covers all relevant behaviors: query semantics, type filtering, fallback, parameter deprecations, geo-bias, result shape, and default limits. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaningful per-parameter semantics beyond the schema: lat/ng verified ignored, types only applied when query is provided and silently ignored on fallback, view affects response fullness, and limit is honored. This directly helps an agent choose parameter values correctly.

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?

The description begins with a specific verb-resource pair, 'Search AllTrails by name,' and clearly differentiates this free-text search tool from sibling get/resolve/list tools. It explains the underlying suggestions endpoint and the result set can mix record types, making the tool's scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use the tool, such as when a free-text query is needed, and explains how to narrow results with types. It also documents the no-query fallback behavior, but it does not explicitly name sibling alternatives or state when not to use this tool in favor of, say, alltrails_get_trail or alltrails_resolve_location.

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