Skip to main content
Glama

Skip a routine's next run

skip_routine
DestructiveIdempotent

Skip the next run of one of this person's routines in Alexein ("no brief tomorrow", "skip this week's PR summary"), by the id list_routines gives. The runs after it go ahead as usual.

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": "skip_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe routine's id, from list_routines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds the blast-radius detail that matters most here: only the next occurrence is suppressed while subsequent runs continue normally. It does not mention permissions, whether a skip can be undone, or what happens if the run is imminent.

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 front-loaded sentence with the effect scope stated before the parenthetical illustrations. No filler, and the examples earn their space by disambiguating intent.

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 one-parameter mutation with full schema coverage and complete annotations, the description supplies everything an agent needs: what it does, how to source the id, and the exact extent of the effect. Nothing material is missing.

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?

With one parameter at 100% schema coverage, the schema already documents the id and its length bounds. The description reinforces provenance ("from list_routines"), which is a small but real addition; the 3 baseline applies since the schema carries the semantics.

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 ("Skip the next run of one of this person's routines") with a precise scope qualifier: only the next run, later runs proceed. The reference to list_routines for obtaining the id separates it from the sibling it depends on.

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 concrete use-case examples in the user's own words ("no brief tomorrow", "skip this week's PR summary") and names list_routines as the way to get the id, so the agent knows both when and how to call it. It does not spell out when not to use it, e.g. skipping an entire routine versus one occurrence.

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