Skip to main content
Glama
xunji-private-mcp

xunji-private-mcp

by Vdk1639

get_training

Read-only

Retrieve a day's training records, with optional full details for heart rate, rest times, RPE, and unfinished sets.

Instructions

Get training for one day. Use full data for heart rate, rest times, RPE and unfinished sets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "datestr": "<datestr>"
    },
    "name": "get_training"
  }
}

Input Schema

NameRequiredDescriptionDefault
datestrYes
include_full_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, open-world operation, so the safety profile is covered. The description adds useful domain context by naming the fields available when full data is requested, but it does not describe what the default response includes or any date/time interpretation rules.

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 two short sentences with no wasted wording, and it front-loads the primary purpose before mentioning the full-data option. Every sentence carries information the caller can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with no output schema and 0% schema description coverage, the description is thin. It does not explain what a normal training response contains, what shape the data takes, or how the required datestr parameter should be interpreted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It partially explains include_full_data by listing the data it unlocks, but it says nothing about datestr beyond implying a single day, leaving required format and date semantics to the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: retrieve training for a single day. It is clear enough to distinguish a daily read from sibling write operations like upsert_training, though it does not clarify exactly what a 'training' record contains.

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?

The only guidance is to use full data for heart rate, rest times, RPE, and unfinished sets, which is about a parameter rather than when to choose this tool over alternatives. It does not say when not to use the tool or name any sibling alternative.

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