Skip to main content
Glama
Sign In

Privatrak

by com.privatrak
OverviewDiscussionsAdmin

Delete a feature rule

delete_feature_rule
DestructiveIdempotent

Delete a feature rule. Its events stop counting as the feature everywhere, past included, unless a data-track name or another rule of the same name covers them; other features are unaffected. undo_setup_run recreates it exactly, with its original id and creation time. 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": {
      "rule_id": "<rule_id>"
    },
    "name": "delete_feature_rule"
  }
}

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).
rule_idYesFeature rule ID, from list_feature_rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds material context beyond them: the exact blast radius (events stop counting everywhere including historical data, unless a data-track name or another rule of the same name covers them), the fact that other features are unaffected, and that undo_setup_run restores the rule with its original id and creation time.

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?

Front-loaded with the operation and its effect, then the undo path, then the run_id branch. Every sentence carries information, though the final run_id sentence is long and packs several instructions together rather than being crisply split.

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 destructive mutation with no output schema, the description covers effect scope, exceptions, reversibility via undo_setup_run, and run_id lifecycle (including the returned id). Nothing an agent needs to invoke this safely and correctly is missing.

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

Parameters4/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. The description nonetheless adds meaning beyond the schema for run_id: it warns never to pass an empty string, explains the new-chat-run behavior, and states that the returned run_id should be carried on every later change. project and rule_id are left to the schema, so this is above baseline but not exhaustive.

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 (delete) and resource (feature rule) and immediately distinguishes itself from siblings by describing the exact effect: events stop counting everywhere, past included, with other features unaffected. An agent can tell this apart from delete_dashboard, delete_funnel, and update_feature_rule without opening a schema.

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

Usage Guidelines4/5

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

Gives explicit guidance on the run_id branch (pass it to undo together with the setup, leave it out to start a new chat run) and names undo_setup_run as the recovery path with exact recreation semantics. It stops short of a full when-not-to-use statement (e.g. update_feature_rule as the non-destructive alternative), so it is clear context without exclusions.

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