Skip to main content
Glama
Sign In
OurFamilyWizard MCP

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get AllTrails list items

alltrails_get_list_items
Read-onlyIdempotent

Fetch the trails saved in an AllTrails list by numeric list id, returning slim trailId references, curator order, and notes; use view:full for complete 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

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.1.9
    • addedInput schema / properties / listId / 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 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"
+}
  4. Addedv2.0.0

TDQS

A4.2/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. The description adds real context beyond them: items are sparse references rather than trail details, entries are sorted by curator order by default, and view:"full" returns raw records in arrival order. It does not mention pagination or item-count limits.

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?

Front-loaded with the core action and id source, then the return-shape caveat. Two dense sentences with little waste, though the view explanation overlaps the schema's own description.

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?

With no output schema, the description steps in to describe the returned fields, their sparsity, and sorting. An agent has enough to call it correctly and know it must hydrate trail details separately.

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 view enum is thoroughly documented in the schema itself, so the description's summary of compact/full largely restates it. Baseline 3 is appropriate when the schema carries the parameter burden.

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+resource ('get the trails saved in an AllTrails list') with the keying input (numeric list id). It explicitly differentiates from siblings by naming alltrails_list_user_lists and alltrails_search as id sources and alltrails_get_trail as the hydration path for trail details.

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?

Gives clear provenance for the list id and a routing rule ('hydrate with alltrails_get_trail'), plus when to switch to view:"full". It stops short of an explicit when-not-to-use statement, but the alternative-tool routing is concrete.

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