Skip to main content
Glama
Sign In
YAZIO MCP

YAZIO MCP

by tomastaker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Exercises

get_exercises
Read-onlyIdempotent

Fetch training and custom exercise entries for a specified date to review your workout history and monitor fitness progress.

Instructions

Returns training and custom training entries for a date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_exercises"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds that it returns both training and custom training entries but doesn't disclose any additional behavioral details such as whether date is required or how results are organized.

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 a single, front-loaded sentence that clearly states the action and scope with no superfluous words.

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?

For a simple read tool with an output schema and comprehensive annotations, the description is mostly complete. However, it leaves ambiguity around the optional date parameter and the exact content of 'training' entries.

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?

The description mentions 'for a date' which gives meaning to the single parameter, but it doesn't specify format or clarify that the parameter is optional (required=0). It provides some compensation for the 0% schema coverage but lacks completeness.

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 clearly states the tool returns training and custom training entries for a date, using a specific verb and resource. It distinguishes from sibling tools like get_diary and get_daily_summary which are broader in scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_diary or get_daily_summary. The only implied usage is that it filters by date, but there is no explicit context or exclusions.

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