Skip to main content
Glama

List my repeating wake-ups

schedule_list
Read-only

List your repeating wake-ups, oldest first: status (active, paused or parked), next_run_at and run counts. With schedule_id: that one and its newest runs (status, attempts, errors, idempotency_key); an unknown schedule_id answers schedule_not_found. Works after the plan ended. One-shot calls: wakeup_list.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "wkp_exampleexampleexample2"
    },
    "name": "schedule_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
runsNoWith schedule_id: how many recent runs (default 20).
instance_idYesUtility instance id from buy or list_utilities.
schedule_idNoOnly this rule, with its recent runs.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "wkp_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds ordering, per-mode return fields, the default of 20 runs, and an explicit error outcome ('an unknown schedule_id answers schedule_not_found'). The only notable gap is that it does not say whether the top-level list is bounded or paginated, which matters for an agent deciding whether one call is enough.

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

Conciseness4/5

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

Front-loaded with the resource and its default behavior, then the detail mode, then the alternative sibling. It is dense and nearly waste-free, though the telegraphic fragments ('status (active, paused or parked), next_run_at and run counts') read more like notes than prose.

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?

There is no output schema, so the description must carry return semantics, and it does so for both modes, plus error behavior and persistence after plan end. What is left unspecified is the size/shape boundary of the top-level listing (result limit or pagination) and whether runs include timing data beyond status, attempts, errors and idempotency_key.

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 100%, so instance_id, schedule_id, runs and passport_token are already documented, including that runs applies only 'with schedule_id' and defaults to 20. The description restates the schedule_id mode but adds no format, range, or interaction detail beyond the schema, which is the expected baseline when the schema carries the load.

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?

Names a specific verb and resource ('List your repeating wake-ups') and immediately enumerates the returned fields (status, next_run_at, run counts) plus ordering ('oldest first'). It also explicitly separates the two modes (list vs. single-schedule detail with runs) and names the sibling that covers the other case ('One-shot calls: wakeup_list').

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

Usage Guidelines5/5

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

Routes the agent explicitly to wakeup_list for one-shot calls, and states the condition that switches this tool into detail mode ('With schedule_id: that one and its newest runs'). It also removes a likely hesitation point by noting 'Works after the plan ended', which tells the agent this is still valid post-plan.

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.