Skip to main content
Glama
Sign In
sisrun-mcp

sisrun-mcp

by cdutr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_week

Retrieve the training plan for the week containing a specified date (YYYY-MM-DD). Use this to answer questions about prescribed workouts, noting that moving far from the current week costs one request per week hop.

Instructions

The training plan for the week containing date (YYYY-MM-DD). Navigating far from the current week costs one request per week hop.

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": {
      "date": "<date>"
    },
    "name": "get_week"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

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?

No annotations are provided, so the description carries the burden. It discloses a non-obvious behavioral trait: each week hop away from the current week costs an extra request. It does not discuss edge cases or invalid dates, but it gives the agent useful insight 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 sentences, front-loaded purpose, no filler. It states what the tool does and then adds the cost caveat efficiently.

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?

The tool has only one required parameter, an output schema exists, and the description covers parameter format and an important behavioral cost. It could be more complete by explicitly naming which sibling to use for current or upcoming weeks, but the essentials for invoking it correctly are present.

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 only says date is a string, so the description's 'YYYY-MM-DD' format and statement that the week contains that date add critical meaning. With 0% schema coverage, the description compensates well for the tool's one parameter.

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 clearly states the tool returns 'the training plan for the week containing date', making the resource and action identifiable. It does not explicitly distinguish itself from get_current_week or get_upcoming, but the purpose is unambiguous.

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 cost note ('Navigating far from the current week costs one request per week hop') implies that dates far from the current week should be avoided when possible, but it never says when to use this tool rather than get_current_week or get_upcoming. The usage context is implied, not explicit.

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