Skip to main content
Glama

List my wake-up calls

wakeup_list
Read-only

List the one-shot wake-up calls of your wake-up-calls plan (wkp_...), up to 200, earliest first, finished ones too (keep wakeup_schedule's id for wakeup_cancel). Status: scheduled, retrying (a try failed and the next one is coming), firing, fired, failed or canceled. Works after the plan ended. Repeating ones: schedule_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": "wakeup_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
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. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds genuinely non-obvious behavior: a 200-item cap, 'earliest first' ordering, and inclusion of finished entries. It also defines the status vocabulary, including what 'retrying' means, which the agent cannot infer from structured data. It stops short of saying what the items contain or whether truncation is signaled, so it is not exhaustive.

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?

Scope, ordering, statuses and the sibling hand-off all land in the first few clauses, and no sentence is filler. The telegraphic phrasing ('Status: scheduled, retrying (a try failed and the next one is coming), firing...') is dense but slightly choppy, costing it a point on readability rather than on length.

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

Completeness5/5

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

For a read-only list tool with no output schema, the description supplies what an agent actually needs: what is returned, how many, in what order, which statuses appear, and that terminated plans still work. Nothing material for correct invocation is left unstated.

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%, so both parameters are already documented in the schema. The description contributes only the 'wkp_...' prefix hint tying instance_id to a wake-up-calls plan; passport_token is not addressed at all. That matches the baseline for a fully documented two-parameter schema.

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?

The description opens with a specific verb and resource ('List the one-shot wake-up calls of your wake-up-calls plan (wkp_...)') and immediately scopes it against the sibling that handles the other case ('Repeating ones: schedule_list'). An agent can distinguish wakeup_list from schedule_list and wakeup_schedule without opening any schema.

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?

It explicitly routes by kind: one-shot calls here, repeating ones to schedule_list, and it ties the returned id forward to wakeup_cancel ('keep wakeup_schedule's id for wakeup_cancel'). It also removes a common doubt up front with 'Works after the plan ended,' so the agent knows a finished plan is not a reason to skip this call.

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.