Skip to main content
Glama

List autopilot schedules

list_schedules
Read-onlyIdempotent

Recurring schedules that post a plan's content: cadence, timezone, approval mode, next run and how many runs so far.

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 observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered and the bar is lower. The description adds the useful fact that a schedule record carries cadence, timezone, approval mode, next run and run count, but says nothing about whether disabled schedules are included, whether results are scoped to a workspace/plan, or how many come back.

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?

One compact clause with zero waste, and the field enumeration is front-loaded. The missing predicate is a small structural weakness: it reads as a catalog entry rather than a statement of what the tool does.

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

Completeness3/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 has to carry the return-value burden, and it does so partially by naming five fields of a schedule. It stops short of covering scope, ordering, or whether the list is filtered or paginated, which leaves real gaps for a listing tool.

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 semantics to explain and the baseline is 4. The description correctly implies an unfiltered listing rather than contradicting the empty schema.

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?

The description scopes the resource precisely: 'recurring schedules that post a plan's content', which separates it from list_plans and list_publish_queue by making clear these are repeat-posting schedules rather than plans or a one-off queue. It is a noun phrase with no verb, so the 'list' action is only inferable from the name and title, but the resource itself is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — nothing says to call this when checking what will auto-publish next, and no siblings (list_publish_queue, list_plans) are named or excluded. The agent must infer the trigger condition entirely from the name.

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