Skip to main content
Glama
Plenera MCP

Plenera MCP

Official
by Plenera-io

list_recurring

Read-only

List a project's recurring schedules with their next UTC occurrence and last issue or error so agents can monitor timing and automation health.

Instructions

List project recurring schedules, their next UTC occurrence and last issue or error.

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

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing what comes back — the next occurrence rendered in UTC and the last issue or error — which is not derivable from the annotations. It stops short of describing pagination, ordering, or behavior for schedules with no prior runs.

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?

A single well-formed sentence with the action front-loaded and the return preview trailing. No filler, no redundant restatement of the tool name.

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 one-parameter read tool with annotations covering safety and no output schema, this is close to complete: the agent knows what it lists and roughly what it gets back. The remaining gap is the format of the required project argument and any result-size limits.

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?

With one parameter at 0% schema description coverage, the description has to carry the burden, and it only implies that the parameter scopes results to a project. It never clarifies whether 'project' expects an ID, key, or name, nor what happens for an unknown project, so it only partially compensates for the coverage gap.

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+resource ("List project recurring schedules") and even previews the returned fields (next UTC occurrence, last issue or error). The read-only nature of the verb cleanly separates it from siblings like create_recurring and update_recurring, though the description never names those alternatives explicitly.

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, no mention of prerequisites, exclusions, or alternatives such as get_issue or query_issues for inspecting past runs. The only usage signal is the implicit 'list schedules for a project' reading of the name.

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