Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List AllTrails completed trails

alltrails_list_completed_trails
Read-onlyIdempotent

List completed AllTrails trails for the signed-in user or a given userId, returning compact summaries or full records for progress tracking.

Instructions

List the trails an AllTrails user has marked completed. Defaults to the signed-in user; pass a userId to target a specific public profile. Returns slim trail summaries (name, length, elevation, difficulty, rating) 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, trails: [...] } in the same slim shape as alltrails_search trails; "full" returns AllTrails' whole trail records.
userIdNoNumeric AllTrails user id. Defaults to the signed-in user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.1.9
    • addedInput schema / properties / userId / pattern
      Added value: +"^\\d+$"
    • 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, trails: [...] } in the same slim shape as alltrails_search trails; \"full\" returns AllTrails' whole trail records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  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. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the bar is lower. The description adds real behavioral context: default response is slim summaries (name, length, elevation, difficulty, rating) and view:"full" returns whole records. It does not cover pagination or result limits for a potentially long completion history.

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?

Three tight sentences with zero filler, front-loading the core action, then targeting rule, then return-shape control. Every sentence earns its place.

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 usefully pre-announces the return shape (slim summary fields vs full records) and the default user scoping, which is enough for correct invocation. Minor gap: no mention of pagination or how the trailing result set is bounded.

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 both view and userId are already well documented (enum values, compact vs full shapes, numeric userId pattern). The description restates the userId default and view:'full' behavior but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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: 'List the trails an AllTrails user has marked completed.' This is clearly distinguishable from siblings like alltrails_search (discovery), alltrails_get_list_items (user lists), and alltrails_get_trail (single trail detail).

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 selection context: defaults to the signed-in user, or pass a userId to target a specific public profile. It does not explicitly name an alternative tool or state when not to use this one (e.g., vs. alltrails_get_activity_feed), but the targeting rule is unambiguous.

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