Rally MCP Server

commission_calculator

Estimate affiliate earnings for a product using daily clicks, conversion rate, and commission percentage.

Instructions

Calculate expected affiliate earnings for a product based on clicks, conversion rate, and commission percentage.

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": {
      "product_price": "<product_price>",
      "commission_rate": "<commission_rate>",
      "daily_clicks": "<daily_clicks>"
    },
    "name": "commission_calculator"
  }
}

Input Schema

Name	Required	Description
`product_price`	Yes	Product price in BRL
`commission_rate`	Yes	Commission rate (0-100)
`daily_clicks`	Yes	Estimated daily clicks
`conversion_rate`	No	Conversion rate (0-1)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations, so description must cover behavioral traits. It doesn't state that this is a read-only computation, nor does it disclose any assumptions or side effects. Default values are in schema but not mentioned.

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

Conciseness5/5

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

Single sentence, no redundant information. Efficiently conveys purpose.

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

Completeness3/5

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

Lacks output format description and edge cases. With no output schema, more detail on return value would be helpful. Adequate but incomplete.

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 covers all parameters with descriptions (100% coverage). Description adds no extra meaning beyond listing inputs; baseline 3 is appropriate.

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?

Description clearly states it calculates expected affiliate earnings with specific inputs (clicks, conversion rate, commission percentage). While it doesn't explicitly differentiate from siblings, the purpose is specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives like analyze_product. No when/when-not instructions provided.

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

Deploy Server