Skip to main content
Glama

Kariaa Agents

My earnings

my_earnings
Read-only

Use when the person asks about their Kariaa balance or payouts. The signed-in person's Kariaa balance, earnings, and payout requests. Platform earnings stay on those platforms.

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": "my_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
balanceNoCurrent payable balance: amount and currency
entriesNoRecent ledger credits
methodsNoSupported payout methods: paypal, venmo, giftcard, crypto
payoutsNoRecent payout requests
pendingNoAmount currently in an open payout request
min_payoutNoMinimum balance required to request a payout
total_earnedNoLifetime earned: amount and currency

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine value by scoping results to the signed-in person (auth requirement) and by stating that platform earnings stay on those platforms, which prevents the agent from assuming cross-platform aggregation. It doesn't discuss result volume or freshness, but the output schema exists to carry return shape.

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?

Three tight sentences with no filler. The usage sentence leads, which is slightly odd given the purpose only arrives in sentence two, but both are short enough that nothing is buried. "Platform earnings stay on those platforms" is compact but relies on the reader to infer what 'platform' means.

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?

With no parameters, an output schema present, and read-only annotations, the description covers the remaining burden: who the data belongs to and what categories it includes. The only soft spot is the vague cross-platform caveat, which an agent might misread without knowing which platforms are in scope.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify beyond confirming the implicit 'current user' filter, which it does. No parameter-level gaps exist to compensate for.

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 names a specific resource set — the signed-in person's Kariaa balance, earnings, and payout requests — so an agent knows exactly what data this returns. It doesn't explicitly contrast with siblings like request_payout or my_submissions, but the resource scope 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 Guidelines4/5

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

"Use when the person asks about their Kariaa balance or payouts" gives a concrete trigger condition. What's missing is routing guidance for adjacent intents — notably that request_payout (not this tool) actually initiates a payout, even though payout requests appear in the results here.

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.