Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

save_pipeline

Destructive

Save reusable PubMed search pipeline configurations by name, tags, and scope, so agents can load and rerun complex queries later.

Instructions

Save a pipeline configuration for later reuse.

The config format is identical to unified_search's pipeline parameter (YAML or JSON). Saved pipelines can be loaded later by name: unified_search(pipeline="saved:weekly_remimazolam")

Args: name: Unique identifier (alphanumeric + hyphens/underscores, max 64 chars). Overwrites if name already exists (upsert semantics). config: Pipeline YAML/JSON string. Same format as unified_search pipeline param. tags: Bounded array of canonical tags (e.g., ["anesthesia", "sedation"]). description: Human-readable description of the pipeline's purpose. scope: Storage scope - "workspace" (project-level, git-trackable), "global" (user-level, cross-project), or "auto" (workspace if available, otherwise global). Default: "auto".

Returns: Confirmation with pipeline metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
tagsNo
scopeNoauto
configYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / config / maxLength
      Added value: +100000
    • addedInput schema / properties / config / minLength
      Added value: +1
    • addedInput schema / properties / description / maxLength
      Added value: +2000
    • 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})$"
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "auto",
+  "workspace",
+  "global"
+]
    • addedInput schema / properties / tags / anyOf
      Added value: +[
+  {
+    "items": {
+      "maxLength": 64,
+      "minLength": 1,
+      "pattern": "^[A-Za-z0-9](?:[A-Za-z0-9_.-]{0,63})$",
+      "type": "string"
+    },
+    "maxItems": 20,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / tags / default
      Previous value: -""New value: +null
    • removedInput schema / properties / tags / type
      Removed value: -"string"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "save_pipelineOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.16

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful behavior beyond that: upsert/overwrite semantics on name collision, the three-way scope meaning (workspace = git-trackable, global = cross-project, auto = fallback), and a return summary. One tension is worth noting: 'upsert semantics' implies repeated identical calls converge, while idempotentHint=false, and the description does not resolve this.

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?

Front-loaded with purpose and format, then Args and Returns blocks that are easy to scan. The name constraint partially restates the schema's pattern/maxLength, a small redundancy, but otherwise every line carries information.

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

Completeness5/5

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

For a 5-parameter mutation tool with no output schema and empty schema descriptions, the definition covers all parameters, the config format, storage-scope semantics, overwrite behavior, and the retrieval path. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: scope is spelled out with each enum's storage implication and default, tags are described as bounded canonical tags with an example, config is tied to the unified_search pipeline format, and name's uniqueness/overwrite behavior is stated. This fully compensates for the empty schema descriptions.

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 (save) and resource (pipeline configuration) plus the reuse intent. It is clearly distinguishable from siblings like list_pipelines, load_pipeline, delete_pipeline, and schedule_pipeline without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the practical workflow: config format matches unified_search's pipeline param, and saved pipelines are retrieved via unified_search(pipeline="saved:name"), which tells the agent what this tool pairs with. It stops short of explicit when-not guidance or prerequisites (e.g., overwrite risk is mentioned but not framed as a caution).

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