Skip to main content
Glama

Wellness Project

by ai.wellnessproject
OverviewDiscussionsAdmin

list_runs

Read-onlyIdempotent

List runs within a date range, or return full saved detail for one run when run_id is provided. Range reads stay compact and return a Runner State summary first. A run_id read returns that run's stored splits and structured segments plus the detailed metrics Elias needs for interval analysis.

Maximum range: 92 days. Defaults to 7 days ago through today. For a longer span, make several calls covering consecutive windows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idNoSpecific run UUID. When provided, returns the full saved run including splits and structured segments and ignores the date range.
end_dateNoEnd of date range. Format: YYYY-MM-DD. Optional. Defaults to today.
start_dateNoStart of date range. Format: YYYY-MM-DD. Optional. Defaults to 7 days ago.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesHuman-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / end_date / description
      Previous value: -"End of date range. Format: YYYY-MM-DD. Optional — defaults to today."New value: +"End of date range. Format: YYYY-MM-DD. Optional. Defaults to today."
    • addedInput schema / properties / run_id
      Added value: +{
+  "description": "Specific run UUID. When provided, returns the full saved run including splits and structured segments and ignores the date range.",
+  "type": "string"
+}
    • changedInput schema / properties / start_date / description
      Previous value: -"Start of date range. Format: YYYY-MM-DD. Optional — defaults to 7 days ago."New value: +"Start of date range. Format: YYYY-MM-DD. Optional. Defaults to 7 days ago."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive, so the description is free to add behavioral value. It does: range reads 'stay compact and return a Runner State summary first,' run_id reads return 'stored splits and structured segments plus detailed metrics,' and the 92-day maximum with multi-call guidance is a meaningful constraint beyond the schema.

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?

Two short paragraphs front-load the primary distinction and then add behavioral and constraint details. Every sentence earns its place: the mode split, the output differences, the defaults, and the multiple-call instruction. No filler or repetition of schema content.

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 three optional parameters, 100% schema coverage, an output schema, and full annotation coverage, the description fills the remaining gaps: output shape per mode, maximum range, defaults, and how to handle spans longer than 92 days. Nothing an agent needs to invoke this tool correctly is missing.

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?

The schema already documents all three parameters with formats and defaults, so baseline is 3. The description adds the 92-day maximum range and clarifies the distinction between compact range output and detailed run_id output, reinforcing parameter behavior beyond the schema without repeating it.

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 opens with a specific verb and resource: 'List runs within a date range, or return full saved detail for one run when run_id is provided.' This clearly distinguishes the two modes of operation and their triggers, so an agent knows exactly what the tool does and when each mode applies.

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 usage context: date-range reads return a compact summary, run_id reads return split and segment detail, and long spans require multiple calls covering consecutive windows. It does not explicitly name alternatives like show_runs, so sibling differentiation is left to inference, but the usage conditions themselves are concrete and actionable.

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

All Wellness Project toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources