Skip to main content
Glama

Set a program goal

set_program_goal
DestructiveIdempotent

Adds or replaces (by id) a measurable goal on the athlete's program. Forks a preset first.

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": {
      "goal": "<goal>"
    },
    "name": "set_program_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
programNameNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

With annotations declaring destructiveHint=true and idempotentHint=true, the description's 'replaces (by id)' is consistent and reinforces the replace-in-place behavior. 'Forks a preset first' adds genuinely non-obvious side-effect context that annotations cannot express. It does not say what data is lost on replacement, so it falls short of a 5.

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 tight sentences with the core action and its upsert semantics front-loaded, followed by the side effect. No filler, no repetition of the title.

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?

This is a destructive mutation taking a nested five-field object with zero schema description coverage and no output schema. The description omits the meaning of metric/target/exerciseId, the effect of omitting programName, and what 'forks a preset' entails, leaving real gaps for an agent filling in the nested payload.

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% and the schema nests five required sub-fields (id, title, exerciseId, metric, target) plus programName, yet the description only mentions 'id'. It says nothing about what 'metric' enumerates (hold_seconds, reps, weight_kg), what 'target' measures, or what omitting programName does.

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 names a specific verb pair and resource: 'Adds or replaces (by id) a measurable goal on the athlete's program.' The '(by id)' clause makes the upsert semantics explicit, so an agent knows this is the write counterpart to remove_program_goal. It stops short of naming any sibling directly, which keeps it from a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance against alternatives like remove_program_goal or the other set_program_* tools. The phrase 'Forks a preset first' hints at a prerequisite workflow but does not state when an agent should choose this tool or what condition triggers it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources