Skip to main content
Glama
Sign In
sisrun-mcp

sisrun-mcp

by cdutr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_upcoming

Fetch prescribed workouts from today onward, covering the current week and up to 8 future weeks, so you can review your upcoming training schedule.

Instructions

Prescribed workouts (status Proposto) from today forward, across the current week plus weeks_ahead future weeks (default 1, max 8).

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_upcoming"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeks_aheadNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

There are no annotations, so the description carries the burden of behavioral disclosure. It explains the status filter, exclusion of past workouts, and the configurable future-week window, which are the key behavioral characteristics needed by an agent.

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?

A single, tight sentence covers purpose, status filter, time window, default, and max. No filler or redundant restating of the tool name.

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 one-parameter getter with an output schema, the description provides enough information to understand what the tool returns and how the parameter behaves. It could be improved by acknowledging the sibling tools and clarifying ordering, but nothing critical 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 input schema only provides the type and default, but the description adds semantic meaning: weeks_ahead controls the number of future weeks beyond the current week, with a default of 1 and max of 8. This makes the parameter's effect clear.

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 identifies a specific resource (prescribed workouts) and a specific status filter (Proposto) with a clear time window (today forward through future weeks). It does not explicitly mention sibling tools, but the 'today forward' scope differentiates it from get_current_week and get_week well enough.

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

Usage Guidelines3/5

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

The time window implies the intended use: retrieving upcoming proposed workouts. However, it does not give explicit guidance on when to choose this over get_current_week or get_week, nor when not to use it.

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