Skip to main content
Glama

List schedules

list_schedules
Read-only

List the company's scheduled exports: the saved query each runs, its cron cadence and timezone, its destination (Google Sheets tab or Slack channel), whether it is enabled, its last and next run, and the last error. Check here before create_schedule, since a saved query can have only one schedule, and to find the id for run_schedule_now. Read-only, takes no parameters.

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

Output Schema

NameRequiredDescriptionDefault
schedulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

The description confirms the operation is read-only and parameterless, and adds a genuinely useful domain constraint (one schedule per saved query) that annotations cannot express. It is only slightly redundant with readOnlyHint=true, and it correctly does not attempt to describe return values since an output schema exists.

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 what is listed before the usage routing. Every clause carries information: the enumerated fields, the uniqueness constraint, and the id-consumer relationship.

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?

With 0 parameters, an output schema covering return values, and annotations carrying the safety profile, the description supplies exactly the missing pieces: the list contents, the uniqueness constraint, and the sibling routing. Nothing an agent needs to call this correctly is absent.

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 and the description states this explicitly ('takes no parameters'), consistent with the empty schema. There is no parameter meaning to add, so the baseline applies.

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 company's scheduled exports') and then enumerates the exact fields returned (cron cadence, timezone, destination, enabled flag, last/next run, last error). This is far more concrete than the title and makes the tool trivially distinguishable from siblings like list_queries or get_query.

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 gives explicit routing rules: check here before create_schedule because a saved query can only have one schedule, and use this to obtain the id needed by run_schedule_now. Both a when-to-use and a downstream-tool dependency are named, leaving nothing to inference.

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