Skip to main content
Glama

Save a pull

save_pull
Destructive

Save a historical pull under a reusable name to re-run it by name with run_saved; reusing a name moves it to the newly saved pull.

Instructions

Save a pull from history under a name (e.g. 'Monthly revenue by region') so it can be re-run by name with run_saved. Saving a name again moves it to this pull.

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": {
      "pull_id": "<pull_id>",
      "name": "<name>"
    },
    "name": "save_pull"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real value by disclosing overwrite semantics ('Saving a name again moves it to this pull'), but it never says what happens to the source pull in history or whether saving requires any permissions.

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?

Two sentences, no filler, with the core action and the sibling reference front-loaded before the overwrite caveat.

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?

A simple two-parameter tool with no output schema needs little more than this. The only meaningful gap is that pull_id's meaning and the fate of the saved pull in history are left unstated.

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 description coverage is 0%, so the description must carry the burden. It gives an example value for name and explains the re-save behavior for name, but pull_id is never described at all, leaving one of two required parameters undocumented.

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 and resource (save a pull from history) plus the scope of what the saved entry enables: re-running by name with run_saved. That contrast with the sibling run_saved makes the two tools trivially distinguishable.

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?

Explicitly names the counterpart tool (run_saved) and describes the workflow the saved entry feeds into, which gives clear usage context. It stops short of stating when NOT to save or what happens on name collisions beyond the move behavior.

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