Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Set a click problem back to open

reopen_click_problem
DestructiveIdempotent

Take back resolving or ignoring an element: its resolve or ignore is removed and it is back to open (never dismissed), as if it had never been resolved or ignored. This is not the status reopened (Happened again), which the API sets by itself when a resolved element recurs; a Happened again row needs nothing from this tool. Fails when the element is not resolved or ignored. identity: the row's identity from list_click_problems, all five fields exactly as returned (null stays null; a different text or a null for "" is a different element). Pass run_id from start_setup_run so this undoes together with the rest of the setup; leave it out (never "") to start a new chat run, whose run_id is returned and should go on every later change.

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

Input Schema

NameRequiredDescriptionDefault
run_idNoThe setup run this change belongs to, from start_setup_run. Omit to start a new chat run (its id is returned).
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).
identityYesThe row's identity object from list_click_problems (default grouping), all five fields exactly as returned, null where it is null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description still adds real value by spelling out the exact state transition ('as if it had never been resolved or ignored', never 'dismissed'), the failure condition when the element isn't resolved/ignored, and the meaning of omitting run_id (starts a new chat run whose id is returned). It does not contradict the annotations.

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 core action and the 'not the reopened status' clarification are front-loaded, and each sentence carries information. It is dense and slightly overlong, but there is little pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-identity mutation tool with no output schema, the description covers the state change, the error condition, identity matching semantics, and run grouping/return behavior, so an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description goes well beyond it: it explains that identity is the exact five-field object from list_click_problems (null must stay null, and '' is a different element than null), and that run_id should be passed from start_setup_run to undo together or omitted (never '') to open a new chat run whose id must be reused.

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 (undo resolve/ignore) on a specific resource (a click problem) and precisely distinguishes the resulting 'open' state from the API-generated 'reopened' (Happened again) status. An agent can differentiate it from resolve_click_problem and ignore_click_problem without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it (to take back a resolve or ignore) and when NOT to use it (a 'Happened again' row is set by the API itself and 'needs nothing from this tool'), plus it names the sibling source of the input (list_click_problems) and the run grouping tool (start_setup_run).

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