Skip to main content
Glama
aimharder-mcp
by rudeayelo

prepare_activity_publication

Read-only

Prepare an activity entry for publication from a verified gym workout using its source ID, date, variant, and achieved results or loads, with preview and confirmation checks.

Instructions

Prepare one own activity entry from a current verified gym workout. Supply its source ID, activity date, difficulty variant and supported achieved results or actual loads. Historical RM suggestions and prescribed rounds are not achieved performance. Missing EMOM completed rounds, RFT elapsed time/completed rounds, or all achieved values return a draft without a reference. Never infer elapsed time from a time-cap note. Show the source, variant, results, loads, audience, WOD TV and duplicate notices. Current role permission is required on the hosted service. Read writeConfirmationRequired from preparation. Account context exposes separate bookingCreation and activityPublication settings in writeConfirmationPolicy; cancellation and deletion always require confirmation. When true, show the exact preview and obtain separate account-holder confirmation before execution with confirmed: true. When false, an explicit request for this exact action is sufficient; omit confirmed and do not ask for another confirmation. A query or preview-only request never authorizes execution.

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": {
      "sourceActivityId": "<sourceActivityId>"
    },
    "name": "prepare_activity_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
gymIdNo
commentNo
actualLoadsNo
activityDateNo
blockResultsNo
variantLabelNo
sourceActivityIdYes

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnly/openWorld/non-idempotent/non-destructive; the description adds the role-permission requirement, the account-context policy split between bookingCreation and activityPublication, the rule that cancellation and deletion always confirm, and the draft-without-reference outcome. One ambiguity: it tells the agent to execute "with confirmed: true" although no confirmed property exists in this schema, so an agent may misread it as a parameter of this tool rather than of the execute sibling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the confirmation paragraph is well ordered, but the middle section degrades into clipped, jargon-dense fragments ("Missing EMOM completed rounds, RFT elapsed time/completed rounds...") that are hard to parse on first read. The "Show the source, variant, results, loads, audience, WOD TV and duplicate notices" sentence also restates return contents that the output schema already defines.

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

Completeness3/5

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

For a 7-parameter preparation step in a prepare/confirm/execute workflow, the confirmation semantics are unusually well specified, but two parameters are left opaque and the confirmed:true instruction does not map onto any property in a schema with additionalProperties:false. An agent has enough to understand intent yet could still mis-invoke on gymId, comment, or the phantom confirmed flag.

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?

Schema description coverage is 0% across 7 parameters, so the description carries the full burden. It meaningfully covers sourceActivityId, activityDate, variantLabel and the achieved-results inputs, and it adds real semantic rules (historical RM suggestions and prescribed rounds are not achieved performance; never infer elapsed time from a time-cap note), but gymId, comment and the single/male/female sourceAlternative values are never explained.

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?

"Prepare one own activity entry from a current verified gym workout" gives a specific verb (prepare) and resource (activity entry) with scope (own, current verified gym workout). The sibling execute_activity_publication is never named, so the prepare-vs-execute distinction is left to the name prefix and the confirmation paragraph rather than stated outright.

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 final third is an explicit decision procedure: read writeConfirmationRequired from the preparation, ask for confirmation only when true, treat an explicit request as sufficient when false, and never treat a query or preview-only request as authorization. That is strong conditional guidance, though it never explicitly says to call this before execute_activity_publication or when to skip it entirely (e.g., for a workout that was never verified).

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