Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Setup run

get_setup_run
Read-onlyIdempotent

One setup run's changes in the order they were made, each with the definition before and after. A click_problem change is an element's resolve or ignore: created (resolved or ignored), updated (switched, or resolved again) or deleted (set back to open with reopen_click_problem), with the element's identity and kind in before/after. A review change is a saved AI review (created) or an updated one (updated): either a recommendation's status set (update_review_recommendation; before/after hold every recommendation's status) or an edit of the review (update_review; before also carries the whole earlier version).

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

Input Schema

NameRequiredDescriptionDefault
run_idYesSetup run ID, from start_setup_run or list_setup_runs.
projectNoProject ID, from list_projects. Required when this connection covers more than one project; may be left out when it covers one (and with an API key, which belongs to one project).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-open-world operation. Beyond that, the description adds substantial behavioral context about ordering and the meaning of click_problem and review changes, including what before/after contain. It does not cover pagination, empty results, or missing-run behavior.

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?

The purpose is front-loaded in the first sentence, and the remaining detail is relevant to interpreting the returned changes. The prose is dense and parenthetical-heavy, but the complexity of the change taxonomy justifies most of the length.

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?

There is no output schema, so the description must explain return semantics. It does that well for the change payloads, including click_problem and review change variants, but it does not describe the full response envelope, error cases, or whether runs can be empty.

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%, and both parameters are fully documented in the input schema, including where run_id and project come from. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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?

The description states the specific resource and scope: a single setup run's changes, in the order they were made, with before and after definitions. The singular scope clearly distinguishes it from list_setup_runs, and the detailed change taxonomy reinforces what the tool returns.

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: use this to inspect the change history of one setup run. However, the description does not explicitly say when to use it versus list_setup_runs, undo_setup_run, or related review tools, so the agent must infer routing from the singular scope.

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

All Privatrak toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources