Skip to main content
Glama

Send one test run of a repeating wake-up now

schedule_run

Send one test run of a repeating wake-up now (within about a minute): exactly like a real run, with "test": true in the body and the header x-agentmart-schedule-test. Never counted as fired or missed; schedule_list with schedule_id shows how it went. At most 5 per rule per hour; an unknown schedule_id answers schedule_not_found. To test heartbeat alerts: heartbeat_test.

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",
      "schedule_id": "wsc_exampleexampleexample2"
    },
    "name": "schedule_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
schedule_idYesschedule id (wsc_...) from schedule_create or schedule_list.
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",
      +    "schedule_id": "wsc_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.4/5.0
Behavior5/5

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

Goes well past the annotations, which only say the call is a non-destructive, non-idempotent, open-world write. The description adds the test envelope ("test": true in the body plus the x-agentmart-schedule-test header), the side-effect rule that it is never counted as fired or missed, a rate limit of 5 per rule per hour, and the schedule_not_found error for unknown ids.

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?

A single dense paragraph that front-loads the action and its immediacy, then layers the test mechanics, side-effect semantics, rate limit and error case. No sentence is filler, and even the closing pointer to heartbeat_test earns its place.

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?

With no output schema, the description still tells the agent how to verify the result (schedule_list with schedule_id), and it covers limits and failure modes. What the call itself returns is left unstated, which keeps it just short of complete.

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 instance_id, schedule_id and passport_token all documented inline, so the baseline is 3. The description adds only the error behavior for an unrecognized schedule_id and nothing about the other parameters.

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 and resource: sending one test run of a repeating wake-up, immediately (within about a minute). It also marks the boundary against real runs and against the sibling heartbeat_test, so an agent can pick it out 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 Guidelines4/5

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

Explains the testing scenario explicitly ("exactly like a real run" but flagged test) and routes heartbeat-alert testing to heartbeat_test. It does not state a when-not case such as avoiding it for production verification, but the context is clear enough to act on.

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.