Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

alltrails_get_list_items

Read-only

Retrieve trail references from an AllTrails list using its numeric list ID. Includes trail ID, curator order, and notes; use full view for complete list-item records.

Instructions

Get the trails saved in an AllTrails list by its numeric list id (from alltrails_list_user_lists, or a public "list" record from alltrails_search). Items are sparse references: each carries a trailId (hydrate with alltrails_get_trail), the curator's order, and any notes — not trail details. Returns slim { trailId, type, order, notes, addedAt } entries sorted by order by default; pass view:"full" for the whole records.

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 { count, items: [{ trailId, type, order, notes, addedAt }] } sorted by the curator's order; "full" returns AllTrails' whole list-item records in the order they arrived.
listIdYesNumeric AllTrails list id

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-item entries sorted by order (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, items: [{ trailId, type, order, notes, addedAt }] } sorted by the curator's order; \"full\" returns AllTrails' whole list-item records in the order they arrived.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Addedv2.0.0

TDQS

A4.9/5.0
Behavior5/5

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

readOnlyHint already covers the read-only safety profile, and the description adds valuable behavioral facts beyond annotations: sparse item shape, default sort by curator order, compact vs full view semantics, and the explicit warning that trail details are not included. No contradiction with 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 action and input provenance, then gives the sparse-reference warning and return shape. Each sentence carries essential information with no filler or repetition.

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 list-fetch tool with no output schema, the description adequately covers input provenance, output shape, default ordering, the full-view option, and the correct hydration path for trail details. Pagination is not mentioned, but the tool's simplicity makes that non-material.

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 coverage is 100%, so the baseline is 3. The description adds meaning by explaining where listId comes from and that compact is the default view with slim sorted output. However, the view parameter's full behavior is already thoroughly documented in the schema, so the additional semantic value is moderate.

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 states a specific verb and resource ('Get the trails saved in an AllTrails list'), identifies the required numeric list id and its source, and explicitly distinguishes the returned sparse items from trail details, pointing to alltrails_get_trail for hydration. This clearly separates it from sibling tools.

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

Usage Guidelines5/5

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

It tells the agent when to use the tool: after obtaining a list id from alltrails_list_user_lists or a public list from alltrails_search. It also warns that items are not trail details and names alltrails_get_trail as the hydration alternative, so the tool selection versus siblings is explicit.

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