Skip to main content
Glama

get_plan_status

Read-onlyIdempotent

Check whether a workout plan is pending, scheduled, failed, or cancelled on the Apple Watch by passing its plan ID from push_plan or list_plans.

Instructions

Whether a plan reached the Watch: pending (not on the Watch yet), scheduled (with scheduled_for), failed (with the error) or cancelled (the athlete removed it from the Watch).

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": {
      "id": "<id>"
    },
    "name": "get_plan_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlan id as returned by `push_plan` or `list_plans`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already cover readOnlyHint and idempotentHint, so the safety profile is known. The description adds genuine value by disclosing the state machine — pending means not yet on the Watch, scheduled carries scheduled_for, failed carries the error, cancelled was removed by the athlete — which the annotations do not convey. It stops short of saying what happens for an unknown or expired id, or whether states are final.

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?

It is a single sentence with no filler, which is appropriate in size. However, it opens with the grammatically awkward fragment 'Whether a plan reached the Watch', so the key action is not front-loaded and the sentence reads as a clause rather than a complete statement.

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?

With no output schema, the description partially compensates by listing the four possible states and two associated fields, which is the most important missing piece. It is still incomplete for a status-checking tool: nothing is said about the case where the plan is unknown, or about how soon after push_plan a status becomes meaningful.

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?

There is a single parameter with 100% schema description coverage that already says 'Plan id as returned by push_plan or list_plans'. The description adds nothing further about the id, so the baseline of 3 applies.

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

Purpose3/5

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

The description implies the tool reports a plan's sync state and enumerates four states, but it never states the operation as a verb+resource (e.g. 'returns the Watch status of a plan'). It reads more like a definition of the status vocabulary than a statement of what the call does, so an agent must infer the purpose from the title and the parameter.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus siblings such as list_plans or push_plan, and no indication of when to poll it (e.g. after push_plan before it appears on the Watch). Usage must be inferred entirely from the status names.

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