Skip to main content
Glama

path_rerun

Run a delivered analysis again, on its own dataset or a new one: the same tools and mappings, no rebuild. package_id may also be the person's own report link (a /rpt/ link or its rpt_ token) or estimate id (est_); it reruns their newest delivered package for it. Time: as path_resolver quotes.

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

Input Schema

NameRequiredDescriptionDefault
package_idYesA delivered package's id, or the person's own report link (/rpt/ link or rpt_ token) or estimate id (est_). Someone else's link is not found.
dataset_refNoabsent = the package's own dataset
resolution_idNoThe resolution_id from path_resolver's path_input. Pass path_input as given.
idempotency_keyNosend one per rerun; a retry with the same key replays the first call instead of running and charging it again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / description
      Previous value: -"Run a delivered package again, on its own dataset or a new one. Same tools, same mappings; no rebuild."New value: +"RerunInput with an idempotency key, served only while PATH_RERUN_IDEMPOTENCY_KEY=1 (rerun_model)."
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 128,
      +      "minLength": 8,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "send one per rerun; a retry with the same key replays the first call instead of running and charging it again",
      +  "title": "Idempotency Key"
      +}
    • changedInput schema / title
      Previous value: -"RerunInput"New value: +"RerunKeyedInput"
  2. Changed1 schema field changed
    • addedInput schema / properties / package_id / description
      Added value: +"A delivered package's id, or the person's own report link (/rpt/ link or rpt_ token) or estimate id (est_). Someone else's link is not found."
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is supplied. The description adds real value by disclosing that mappings/tools are reused and that timing follows path_resolver's quote, but it omits that the rerun is charged, which the schema alone mentions via the idempotency key wording.

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?

Two dense sentences, with the core action front-loaded before the optional id forms and the timing note. Nothing is redundant, though the trailing 'Time: as path_resolver quotes.' is telegraphic enough to slow an agent briefly.

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 job-launching tool with four parameters there is no output schema, and the description never indicates what a call returns (job id, status handle) or that a rerun consumes compute/credits. The timing pointer to path_resolver and the reuse semantics cover most of what an agent needs, but the post-call picture is incomplete.

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 100%, so all four parameters are already documented, including the id-format caveats and the dataset_ref default. The description restates the package_id flexibility but adds no syntax, format, or meaning beyond what the schema provides, which is the expected baseline.

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 and resource: 'Run a delivered analysis again' with 'the same tools and mappings, no rebuild,' which tells an agent exactly what operation is performed and that it differs from a fresh build. It does not explicitly contrast with siblings like path_reuse or path_tool_run, so differentiation is implied rather than stated.

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?

'no rebuild' implies the boundary against rebuilding, and the description notes package_id accepts a delivered package, /rpt/ link, or est_ id, which is useful selection context. However, it never says when NOT to use this tool or names an explicit alternative path, leaving the routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.