Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

List schedules

list_schedules
Read-onlyIdempotent

List the schedules in the current environment, newest first: kind, spec (env values hidden, env_keys shows their names), run_at or cron and timezone, enabled, next_run_at, run_as and run_as_credential (user, api_key or agent: who each run launches as, and through what), and the last run: last_run_at, last_status (launched, failed, skipped_budget, skipped_overlap, no_access or credential_revoked), last_error, last_instance_id or last_job_id, run_count. A schedule whose scheduled runs failed 5 times in a row is paused (enabled false, last_error says so); once the cause is fixed, update_schedule resumes it.

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
workspaceNoWorkspace ID (optional: defaults to the authenticated workspace)
environmentNoEnvironment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / env
      Removed value: -{
-  "description": "Environment name (optional — defaults to main)",
-  "type": "string"
-}
    • addedInput schema / properties / environment
      Added value: +{
+  "description": "Environment name (optional: defaults to the environment this session acts in)",
+  "type": "string"
+}
    • changedInput schema / properties / workspace / description
      Previous value: -"Workspace ID (optional — defaults to authenticated workspace)"New value: +"Workspace ID (optional: defaults to the authenticated workspace)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context the annotations cannot: env values are hidden with env_keys showing names, last_status enumerates six terminal states, and it discloses the auto-pause rule after 5 consecutive failures plus how to recover via update_schedule.

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?

It is front-loaded with the verb and scope, then moves to return fields and the pause rule. The field enumeration is dense but each item maps to concrete returned data rather than filler; only the long comma chain slightly hurts readability.

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 no output schema, the description effectively substitutes for one by listing every returned field and the possible last_status values. For a read-only two-parameter list tool, an agent has everything needed to call it and interpret results, including the pause/error semantics.

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 description coverage is 100% and both optional parameters (workspace, environment) already document their defaults, so the description adds nothing about parameters. The baseline 3 applies since the schema carries parameter meaning on its own.

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 opening clause states a specific verb and resource ('List the schedules in the current environment'), adds ordering ('newest first'), and immediately enumerates the returned fields, so an agent knows exactly what it gets and can distinguish it from list_jobs or list_environments.

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 scope phrase 'in the current environment' and by the closing pointer that update_schedule resumes a paused schedule, but the description never states when to call this versus siblings such as list_jobs or get_job. No explicit exclusions or prerequisites are given.

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

All Runcrate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources