Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

schedule_pipeline

Destructive

Schedule a saved PubMed search pipeline for periodic execution using a cron expression; optionally store diff-mode and notify preferences.

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. Changed4 schema fields changedv0.7.7
    • addedInput schema / properties / diff_mode / anyOf
      Added value: +[
+  {
+    "default": true,
+    "title": "Diff Mode",
+    "type": "boolean"
+  },
+  {
+    "description": "Explicit true/false text, ignoring ASCII case and surrounding whitespace.",
+    "pattern": "^[ \\t\\r\\n]*(?:[tT][rR][uU][eE]|[fF][aA][lL][sS][eE])[ \\t\\r\\n]*$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / diff_mode / type
      Removed value: -"boolean"
    • addedInput schema / properties / notify / anyOf
      Added value: +[
+  {
+    "default": true,
+    "title": "Notify",
+    "type": "boolean"
+  },
+  {
+    "description": "Explicit true/false text, ignoring ASCII case and surrounding whitespace.",
+    "pattern": "^[ \\t\\r\\n]*(?:[tT][rR][uU][eE]|[fF][aA][lL][sS][eE])[ \\t\\r\\n]*$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / notify / type
      Removed value: -"boolean"
  2. 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
  3. First observedv0.5.16

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is largely covered. The description adds useful behavioral detail about storing diff-mode and notify preferences and returning a confirmation, but it does not explain authorization needs, what exactly is destroyed or replaced, 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?

The description is front-loaded with a one-line summary followed by structured Args and Returns sections, with no wasted prose. The vague 'removal result' clause slightly weakens an otherwise efficient structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive scheduling tool with four parameters and no output schema, the description covers parameter meanings and a basic return type, and the annotations supply safety hints. However, it omits when to choose this tool over unschedule_pipeline and leaves the 'removal result' ambiguous, so an agent still lacks some routing and outcome clarity.

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 description coverage is 0%, so the description carries the burden of explaining parameters. It successfully documents all four parameters, including a concrete cron example and the meaning of diff_mode/notify preference storage, though it does not elaborate on the name pattern or boolean-string nuance already present in the schema.

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 states a specific verb ('Schedule') and resource ('saved pipeline') with the scope 'periodic execution,' making the core action clear. However, the later phrase 'removal result' introduces ambiguity with the sibling tool unschedule_pipeline, preventing perfect clarity.

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?

The description implies usage by saying it schedules a saved pipeline, but it offers no explicit when-to-use guidance, no exclusions, and no mention of the alternative unschedule_pipeline for removing schedules. An agent must infer the routing from the tool name alone.

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