Skip to main content
Glama

Reject a plan revision

reject_plan_revision
DestructiveIdempotent

Reject a pending plan revision when the coach decides against it. Nothing on any calendar changes and no one is notified; feedback is stored with the revision. Rejecting a revision that is no longer pending changes nothing.

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": {
      "revision_id": "<revision_id>"
    },
    "name": "reject_plan_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackNoWhy it was rejected; stored with the revision.
revision_idYesrevision_id from propose_plan_revision or list_plan_revisions.

Output Schema

NameRequiredDescriptionDefault
idNo
kindNo
errorNo
notesNo
scopeNo
org_idNo
reasonNo
sourceNo
statusNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
coach_idNo
warningsNo
next_stepNoWhat can be done next, for example after a failure.
applied_atNo
athlete_idNo
created_atNoEpoch milliseconds.
operationsNo
updated_atNo
apply_errorNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
reviewed_atNo
revision_idNo
total_weeksNo
user_contentNoFields in this result that people wrote.
applied_at_isoNoThe epoch field beside it as a UTC instant; the local day can differ.
coach_feedbackNo
created_at_isoNoThe epoch field beside it as a UTC instant; the local day can differ.
updated_at_isoNoThe epoch field beside it as a UTC instant; the local day can differ.
weeks_returnedNo
reviewed_at_isoNoThe epoch field beside it as a UTC instant; the local day can differ.
plan_instance_idNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
operation_resultsNo
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / $defs / Activity / properties / content_blocks / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "items": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "integer"
      -          },
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "boolean"
      -          },
      -          {
      -            "items": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "integer"
      -                },
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "boolean"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "type": "array"
      -          },
      -          {
      -            "$ref": "#/$defs/LocalizedText"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "type": "array"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "items": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "boolean"
      +          },
      +          {
      +            "items": {
      +              "anyOf": [
      +                {
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "integer"
      +                },
      +                {
      +                  "type": "number"
      +                },
      +                {
      +                  "type": "boolean"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "$ref": "#/$defs/LocalizedText"
      +          },
      +          {
      +            "items": {
      +              "type": "array"
      +            },
      +            "type": "array"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / $defs / Activity / properties / content_blocks / description
      Previous value: -"Interval rows; each row's values follow content_block_fields."New value: +"Workout steps as rows whose values follow content_block_fields; an interval's blocks value is its nested steps as rows in the same columns."
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is already known. The description adds real context beyond that: no calendar changes, no notifications, feedback persisted with the revision, and a no-op for stale revisions. It clarifies rather than contradicts destructiveHint (the 'destruction' is bounded to the revision's status), but it never states permission requirements or whether a rejected revision can be re-proposed.

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?

Three short sentences, front-loaded with the action and condition, followed by effect and edge case. Nothing is padded; each clause carries information an agent would otherwise have to guess.

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?

A simple two-parameter mutation with full schema coverage, an output schema, and complete annotations needs little more. The only meaningful gap is authorization/role context and what a caller can do after rejection, but neither blocks correct invocation.

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 coverage is 100%, with both revision_id (provenance from propose_plan_revision or list_plan_revisions) and feedback already documented in the schema. The description only restates that feedback is stored with the revision, adding no format, length, or optionality guidance beyond structured data, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb ('Reject'), a specific resource ('a pending plan revision'), and the actor ('the coach'). The 'pending' qualifier scopes it precisely and makes it trivially distinguishable from the approve_plan_revision sibling without opening either schema.

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?

Gives a clear triggering condition ('when the coach decides against it') and adds an exclusion case ('Rejecting a revision that is no longer pending changes nothing'), so an agent knows the call is a no-op in that state. It does not explicitly name approve_plan_revision as the alternative path, which keeps it short of a 5.

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