Skip to main content
Glama

list_schedules

List this workspace's scheduled tasks with task, interval, next run, and run count so you can verify active schedules and timing. Secrets are redacted.

Instructions

List this workspace's scheduled tasks (id, task, interval, next run, run count). Secrets redacted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the returned field set plus the notable trait that secrets are redacted. It does not state whether the listing is complete or paginated, what happens in a large workspace, or what permissions are required, so a read-only list tool is only partially characterized.

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?

Two sentences, front-loaded with the action and scope, followed by the return shape and the redaction caveat. Nothing is repeated from the (empty) schema and no clause is filler.

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?

For a zero-parameter read tool with no output schema, the description compensates well by enumerating the returned fields and flagging redaction. The only real gap is the absence of any statement about result size, ordering, or pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add. Baseline 4 applies; the parenthetical is about return values, not inputs.

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

Purpose4/5

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

"List this workspace's scheduled tasks" gives a specific verb plus resource, and the parenthetical enumerates exactly what comes back (id, task, interval, next run, run count). It reads clearly against create_schedule, though it never names a sibling to differentiate against explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the verb and the "this workspace's" scoping, which tells the agent it is a workspace-scoped read with no filtering. There is no explicit when-to-use statement, no mention of when another tool (e.g. get_job) would be preferable, and no prerequisites.

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