Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Ignore a click problem

ignore_click_problem
DestructiveIdempotent

Mark a click problem as intended, e.g. a heading people habitually click: hidden for good, and nothing that happens later brings it back. When something was fixed use resolve_click_problem instead, so a recurrence shows. Overwrites a resolve on the same element; on an element already ignored it changes nothing and says so. Hides rows only: no count changes and no event is deleted. 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": "ignore_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.9/5.0
Behavior5/5

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

Annotations declare destructiveHint/idempotentHint, but the description adds substantial context beyond them: it says the action overwrites a resolve, that re-ignoring an already-ignored element is a no-op that 'says so', and that it 'hides rows only: no count changes and no event is deleted'. That precisely delineates the blast radius of a destructive operation.

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 and the sibling alternative are front-loaded in the first two sentences, and both the identity and run_id rules earn their space. The paragraph is dense with parentheticals, which slightly reduces scannability, but there is little genuine redundancy.

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 mutating, idempotent, run-scoped tool with no output schema, the description covers everything an agent needs: identity matching rules, run_id lifecycle, the overwrite/idempotency behavior, and the fact that rows are only hidden. Nothing material is left unstated.

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%, so the baseline is 3, but the description goes well past it: it specifies that identity is all five fields exactly as returned, that null stays null, and that a different text or a null substituted for "" identifies a different element. It also gives concrete run_id usage rules ('never ""', returned id should go on every later change).

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?

It states a specific verb and resource ('Mark a click problem as intended') and immediately defines the semantics ('hidden for good, and nothing that happens later brings it back'). It explicitly distinguishes itself from the sibling resolve_click_problem, so an agent can separate the two without opening either 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?

It names the alternative condition explicitly: 'When something was fixed use resolve_click_problem instead, so a recurrence shows.' It also covers the run_id routing choice (pass it to undo with the setup, omit it to start a new chat run), leaving nothing to inference.

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