Skip to main content
Glama

OpenPanel: Track revenue

openpanel_track_revenue
Destructive

Track a revenue or purchase event by recording its amount, currency, and optional order details so you can attribute sales to a site and profile.

Instructions

[UNIFIED] Track a revenue/purchase event with amount and currency.

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": {
      "site": "<site>",
      "amount": "<amount>"
    },
    "name": "openpanel_track_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
amountYes
currencyNoUSD
order_idNo
client_ipNo
product_idNo
profile_idNo
propertiesNo
product_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the write/mutation profile is covered structurally. The description adds nothing about what happens on duplicate sends, whether order_id deduplicates, what auth or site scoping is required, or what the destructive hint means for a tracking call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no padding, which is structurally clean. However, the '[UNIFIED]' tag is noise and the brevity comes at the cost of substance rather than in service of it.

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

Completeness2/5

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

With 9 undocumented parameters, no output schema, and mutation annotations including destructiveHint, the description is well short of what an agent needs. It does not explain the return (event id? dedup status?) or the effect of sending revenue data, leaving the heaviest gaps to inference.

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

Parameters2/5

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

Schema coverage is 0% across 9 parameters, and the description only echoes two of them (amount, currency). It says nothing about the required 'site' parameter, the role of order_id, what the string-typed 'properties' payload should contain, or how client_ip, product_id, profile_id, and product_name affect attribution.

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 gives a specific verb and resource: 'Track a revenue/purchase event with amount and currency.' The revenue/purchase qualifier distinguishes it in spirit from the generic event-tracking siblings, though no sibling is named and the '[UNIFIED]' prefix is unexplained jargon that adds no clarity.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of openpanel_track_event or openpanel_track_batch, no prerequisites, and no exclusions. An agent must infer that revenue-specific tracking is the choice for purchases purely from the word 'revenue'.

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

Deploy Server

Other Tools