Skip to main content
Glama

Re-run a pull

rerun
Read-only

Re-execute a past pull from history using its stored SQL unchanged on the same source to reproduce previous query results exactly.

Instructions

Re-run a past pull from history exactly: its stored SQL, unchanged, on the same source.

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": "rerun"
  }
}

Input Schema

NameRequiredDescriptionDefault
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds genuinely new behavior — the SQL is replayed exactly, unmodified, against the same source, so no edits or source swapping occur. It does not address what happens if the source no longer exists or whether the replay incurs cost, which keeps it below a 5.

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 exactness constraint placed before the source constraint; no filler words and nothing repeated from the title or schema.

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 covering the safety profile and no output schema, the description says enough to invoke it correctly. The remaining gap is failure and result semantics when the stored query can no longer be replayed.

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% — pull_id carries only a title — so the description must carry the meaning. "A past pull from history" usefully tells the agent that pull_id refers to an entry in history rather than a saved pull, but gives no format or provenance detail (e.g., where to obtain the id).

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 gives a specific verb and resource ("Re-run a past pull from history") and pins down the scope with "its stored SQL, unchanged, on the same source." The phrase "from history" distinguishes it from the related run_saved sibling without naming it explicitly.

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?

Usage is implied rather than stated: use it when you want to replay an earlier query verbatim. There is no explicit when-not guidance and no named alternative (run_saved and query are obvious neighbors for the case where the SQL needs editing).

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