Skip to main content
Glama
Sign In
agent-pool-mcp

agent-pool-mcp

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_schedules

List all scheduled tasks to see cron expressions, upcoming run times, and whether the daemon is active.

Instructions

List all scheduled tasks with their cron expressions, next run times, and daemon status.

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
cwdNoProject directory. Defaults to current working directory.
jsonNoReturn pure JSON string instead of Markdown format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.3

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It implies a read operation but does not explicitly state it is non-destructive or safe. Minimal transparency beyond the obvious list action.

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?

Single sentence with no wasted words, but slightly sparse. Could be improved by front-loading the key action and adding a brief note about usage.

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 simple list tool with two optional parameters and no output schema, the description adequately covers the return fields. Lacks mention of default behavior or formatting, but sufficient.

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%, so the schema fully describes both parameters (cwd and json). The description adds no additional parameter meaning, meeting the baseline of 3.

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 clearly states the tool lists all scheduled tasks and specifies the fields returned (cron expressions, next run times, daemon status). It distinguishes from siblings like list_tasks by focusing on scheduled tasks, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus siblings such as schedule_task or list_tasks. The description only states what it does without context or alternatives.

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