Skip to main content
Glama

Run a saved pull

run_saved
Read-only

Re-run a saved pull by name to repeat a previously defined query with the same rows and columns, exactly as it was saved.

Instructions

Re-run a saved pull by its name (see saved_pulls), exactly as it was saved.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and non-destructive/non-open-world, so the safety profile is covered. The description adds one valuable behavioral fact — that the pull executes exactly as saved, with no parameter overrides — but says nothing about whether it re-executes against live data, what it returns, or what happens if the name does not exist.

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 front-loaded sentence with the action, the key, and the discovery pointer. No filler, nothing that could be cut without losing information.

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 one-parameter tool with annotations and no output schema, the essentials are present: the action, the required argument, and where to find argument values. Only edge-case behavior (missing name, re-execution semantics) is unaddressed, which is a minor gap at this complexity.

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 parameter burden. It does partially: 'name' is identified as the saved pull's name and the source of valid names is pointed to via saved_pulls. It still omits matching rules (case sensitivity, exact vs partial, ambiguity handling).

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 ('re-run') and resource ('saved pull'), plus the lookup key ('by its name'), and points at the saved_pulls sibling for discovery. It implicitly separates itself from save_pull by saying 're-run', though the contrast is not stated outright.

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?

The parenthetical '(see saved_pulls)' gives a concrete lead on how to obtain a valid name, which is real usage context. However, there is no statement about when to prefer this over running an ad-hoc query, nor about failure modes such as an unknown or deleted saved pull.

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