Skip to main content
Glama
Sign In
Nerdit

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_schedules

Lists a deployed app's schedules, including cron expressions, paths, timezones, next run times, and latest run results for owners or admins.

Instructions

List a deployed app's schedules (owner or admin only).

    Returns ``{service_name, schedules: [{name, cron, path, timezone,
    timeout_s, next_run_at, last_run}]}``. ``next_run_at`` is the next
    occurrence within 8 days (UTC), null when none; a schedule fires only
    while the app is running and healthy. ``last_run`` is the newest run
    (``{run_id, trigger, started_at, finished_at, outcome, status_code}``).

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": {
      "name": "<name>"
    },
    "name": "list_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName (or row id) of an existing deployed app — only kind 'service' can be exposed: ``share_service``/``add_domain`` refuse a model or database with 422 ``*.kind_unsupported``, while the remove tools just find nothing to undo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations to lean on, the description carries the load well: it discloses the auth requirement, the 8-day UTC horizon for `next_run_at`, the null case, and the crucial operational caveat that a schedule only fires while the app is running and healthy. It does not cover ordering of the returned list or error responses, but the core behavioral picture is solid.

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?

The purpose sentence is front-loaded and the return-shape and timing caveats follow in a logical order with no filler. Residual reStructuredText artifacts (double backticks, escaped quotes) add minor noise but cost nothing in comprehension.

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?

There is no output schema, and the description compensates by enumerating the response envelope and the nested fields of both `schedules` and `last_run`. For a single-parameter read tool this is close to complete; only list ordering and failure modes are unaddressed.

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 coverage is 100% and the parameter description already explains the name/row-id semantics and the kind constraint. The description only reinforces that the target is a 'deployed app', adding little beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('List a deployed app's schedules') plus an access scope ('owner or admin only'). It implicitly separates itself from the run-history sibling by describing `last_run` as only the newest run, but it never names `list_schedule_runs`, so an agent must infer the boundary.

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?

The permission precondition ('owner or admin only') is stated, which is useful context for when the call will succeed. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for retrieving run history, so routing is only implied.

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

Deploy Server

Other Tools