Skip to main content
Glama

Estimate Kick sub earnings

estimate_kick_earnings
Read-onlyIdempotent

Estimate a Kick streamer's monthly sub income with Kick's 95/5 split, compared with a 50/50 split. Gifted subs count as subs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estimate_kick_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sub_priceNoSub price in USD.
subs_per_monthNoSubs per month, including gifted subs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral content beyond that: it discloses the 95/5 revenue split, the 50/50 comparison baseline, and that gifted subs are counted, which tells the agent what the computation actually does.

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?

Two short sentences with no filler; the core computation is front-loaded and the gifted-sub rule is a brief clarifying second sentence. Nothing could be removed without losing information.

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

Completeness4/5

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

For a two-parameter pure calculation with fully described schema and annotations covering safety, the definition is nearly complete. It could say more about the returned shape (e.g., dollar figures for both splits), but that is a minor gap given the tool's simplicity.

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% with defaults and units documented for both parameters, so the baseline is 3. The description's note about gifted subs counting as subs slightly reinforces the subs_per_month semantics, but it largely repeats the schema's 'including gifted subs' caveat.

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?

States a specific verb and resource ('Estimate a Kick streamer's monthly sub income') and names the platform, which distinguishes it from the Twitch/TikTok sibling estimators. It does not explicitly say 'not for Twitch', but the platform is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the platform scoping rather than stated; there is no explicit when-to-use or when-not-to-use guidance. For a simple calculator this is largely adequate, but the agent gets no instruction on selecting it over estimate_twitch_earnings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources