Skip to main content
Glama
nitinchakravarthy

Workout Tracker MCP Server

get_workout_plan_from_dynamodb

Retrieve a full workout plan from DynamoDB by user ID and plan ID, including all weeks, workout sessions, and exercises in one call.

Instructions

Retrieve a complete workout plan from DynamoDB

Fetches the entire workout plan structure including:
- Plan metadata (name, goal, duration, status, etc.)
- All weeks in the program
- All workout sessions for each week
- All exercises for each workout session

Args:
    user_id: User ID who owns the plan
    plan_id: Unique plan identifier
    table_name: DynamoDB table name (default: WorkoutPlans)
    region: AWS region (default: us-west-2)

Returns:
    Dictionary containing the complete workout plan with plan_metadata and weeks,
    or error information if the plan is not found or retrieval fails

Example:
    result = get_workout_plan_from_dynamodb(
        user_id="user_123",
        plan_id="plan_abc123"
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNous-west-2
plan_idYes
user_idYes
table_nameNoWorkoutPlans

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well by explaining the full return structure, including plan_metadata and weeks, and by stating that error information is returned when the plan is not found or retrieval fails. It could additionally note that the operation is read-only, but the verb 'retrieve' and the detailed behavior make the tool's effect clear.

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 well-structured with a concise summary, bulleted return contents, a parameter list, a returns explanation, and an example. Every section adds useful information without unnecessary verbosity.

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?

Given there is no output schema and no annotations, the description is remarkably complete: it defines purpose, expected payload structure, all parameters with defaults, return behavior, error handling, and a usage example. An agent has enough information to select and invoke the tool correctly.

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?

The input schema has 0% description coverage, so the description must compensate, and it does. It explains user_id as the plan owner, plan_id as the unique identifier, table_name with its default, and region with its default, plus it provides a concrete example using the required parameters.

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 and resource: 'Retrieve a complete workout plan from DynamoDB.' It then enumerates exactly what is fetched (metadata, weeks, sessions, exercises), which clearly distinguishes it from sibling tools like log_workout or save_workout_plan_to_dynamodb.

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 clearly states the context for use: when a complete workout plan needs to be retrieved from DynamoDB. It does not explicitly name alternatives or state when not to use the tool, but the context is straightforward and the sibling tool for saving is easy to distinguish.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nitinchakravarthy/workout_tracker_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server