Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

schedule_pipeline

Destructive

Automate recurring literature searches by scheduling saved pipelines with a cron expression. Optionally enable diff-mode and notifications for each run.

Instructions

Schedule a saved pipeline for periodic execution.

Args: name: Saved pipeline name. cron: Required 5-field cron expression. Example: "0 9 * * 1" (Mon 9am). diff_mode: When True, store diff-mode preference with the schedule. notify: When True, store notify preference with the schedule.

Returns: Schedule confirmation or removal result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cronYes
nameYes
notifyNo
diff_modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / cron / default
      Removed value: -""
    • addedInput schema / properties / cron / maxLength
      Added value: +200
    • addedInput schema / properties / cron / minLength
      Added value: +1
    • addedInput schema / properties / name / maxLength
      Added value: +64
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / name / pattern
      Added value: +"^[a-z0-9](?:[a-z0-9_-]{0,63})$"
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "cron"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "schedule_pipelineOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.16

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, covering the mutation and external-effect profile. The description adds the cron-field requirement and clarifies that diff_mode/notify are 'stored preferences' rather than immediate actions, but doesn't disclose reversibility, auth needs, or rate limits.

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?

Well-structured with Args/Returns sections and front-loaded purpose statement. The Returns section is somewhat filler since there's no output schema, but overall efficient and easy to scan.

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?

Given four parameters at 0% schema coverage and no output schema, the description supplies the missing parameter semantics thoroughly. The main gap is lack of when-to-use guidance versus sibling pipeline tools.

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?

Schema coverage is 0%, so the description carries the load. It documents all four parameters with meaning beyond the schema (cron field count and a concrete example, name = saved pipeline name, and the storage semantics of the two booleans). This compensates well for the undocumented schema.

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?

States a specific verb (schedule) and resource (saved pipeline for periodic execution). The sibling unschedule_pipeline is the clear inverse, and this description correctly claims the scheduling side without conflating them.

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?

Implies usage (scheduling periodic execution) but never states when to use this versus save_pipeline or load_pipeline, nor any prerequisites like the pipeline already needing to exist. No exclusions or alternatives named.

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