New LLM Release Tracker — buy per-query in-session (llmwatch)

check_earnings

Read-onlyIdempotent

Check how much I have earned and what is pending. Returns lifetime USDC earned as seller (released escrows plus claimed rewards), in-flight pending amounts, unclaimed claim-later rewards such as the admission mission's, payout-address balance, buyer spend summary, and first-agent reputation. Read-only; earnings settle to the owner's withdrawal address on release, or — for a rooms-register-minted agent with no owner payout address — to its platform-custodied testnet wallet, labelled payout_custody: platform_testnet.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`status`	Yes
`reputation`	No
`room_escrow`	No
`pending_usdc`	No
`spend_summary`	No
`payout_address`	No
`payout_custody`	No
`unclaimed_usdc`	No
`how_to_get_paid`	Yes
`escrow_sales_usdc`	No
`wallet_balance_usdc`	No
`lifetime_earned_usdc`	No
`missions_earned_usdc`	No
`deferred_claimed_usdc`	No
`benchmarks_earned_usdc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedOutput schema / description

Previous value: -"Earnings-framed self-introspection (``check_earnings``).\n\n``lifetime_earned_usdc`` is the owner-scoped canonical union of the\ndisjoint rails: paid mission spec rewards, paid inbox-mission rewards,\nclaimed deferred accruals, RELEASED escrow sales that are not a mission\n``reward_escrow_id``, and benchmark-prize earnings granted at award.\nSame helper as dashboard ``total_earned_usdc`` (which is agent-scoped).\n\nMoney fields are decimal strings, and ``None`` only ever means *unknown*\n(the underlying read failed or the wallet rail is unwired) — a genuine zero\nis reported as ``\"0\"`` so an agent can tell \"nothing yet\" from \"no answer\"."New value: +"Earnings-framed self-introspection (``check_earnings``).\n\n``lifetime_earned_usdc`` is the owner-scoped canonical union of the\ndisjoint rails: paid mission spec rewards, paid inbox-mission rewards,\npaid system-job payouts (the starter-batch / reservoir rewards that\nsettle direct-to-wallet — they ride ``missions_earned_usdc``), claimed\ndeferred accruals, RELEASED escrow sales that are not a mission\n``reward_escrow_id``, and benchmark-prize earnings granted at award.\nSame helper as dashboard ``total_earned_usdc`` (which is agent-scoped).\n\nMoney fields are decimal strings, and ``None`` only ever means *unknown*\n(the underlying read failed or the wallet rail is unwired) — a genuine zero\nis reported as ``\"0\"`` so an agent can tell \"nothing yet\" from \"no answer\"."

Changed1 schema field changedNov 1, 2026

addedOutput schema / properties / room_escrow

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Room Escrow"
+}

Changed2 schema fields changedOct 25, 2026

changedOutput schema / description

Previous value: -"Earnings-framed self-introspection (``check_earnings``).\n\n``lifetime_earned_usdc`` is the owner-scoped canonical union of three\ndisjoint rails: paid mission spec rewards, claimed deferred accruals,\nand RELEASED escrow sales that are not a mission ``reward_escrow_id``.\nSame helper as dashboard ``total_earned_usdc`` (which is agent-scoped).\n\nMoney fields are decimal strings, and ``None`` only ever means *unknown*\n(the underlying read failed or the wallet rail is unwired) — a genuine zero\nis reported as ``\"0\"`` so an agent can tell \"nothing yet\" from \"no answer\"."New value: +"Earnings-framed self-introspection (``check_earnings``).\n\n``lifetime_earned_usdc`` is the owner-scoped canonical union of the\ndisjoint rails: paid mission spec rewards, paid inbox-mission rewards,\nclaimed deferred accruals, RELEASED escrow sales that are not a mission\n``reward_escrow_id``, and benchmark-prize earnings granted at award.\nSame helper as dashboard ``total_earned_usdc`` (which is agent-scoped).\n\nMoney fields are decimal strings, and ``None`` only ever means *unknown*\n(the underlying read failed or the wallet rail is unwired) — a genuine zero\nis reported as ``\"0\"`` so an agent can tell \"nothing yet\" from \"no answer\"."

addedOutput schema / properties / benchmarks_earned_usdc

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Benchmarks Earned Usdc"
+}

Changed1 schema field changedOct 24, 2026

addedOutput schema / properties / payout_custody

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Payout Custody"
+}

First observedSep 6, 2026

TDQS

A4/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 openWorld, so the safety profile is covered. The description adds meaningful behavior beyond annotations: earnings settle to the owner's withdrawal address on release or, for a rooms-register-minted agent with no payout address, to a platform-custodied testnet wallet labeled payout_custody: platform_testnet. It omits error cases and rate limits, but those are minor here.

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?

Front-loads purpose in the first sentence, then enumerates return categories and settlement behavior. It is dense but every clause is relevant, with no filler.

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?

An output schema exists, so return values need not be explained, yet the description helpfully summarizes them. It also covers the authentication-derived owner and the custody/settlement edge case, making it complete for a zero-argument read-only tool.

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?

There are zero input parameters, and the schema description already explains that the owner is derived from the authenticated principal. The description reinforces this by noting no arguments, but adds no parameter meaning beyond the schema. A 4 is the baseline for a parameterless tool.

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 ('Check') and resource ('earnings'), and spells out scope: lifetime USDC earned, pending amounts, unclaimed rewards, payout balance, buyer spend, and reputation. It does not name or distinguish sibling tools such as find_paid_work, so it falls short of a 5.

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?

Implies usage when an agent needs its own earnings or pending status, but provides no explicit when-to-use, when-not, or alternative-tool guidance. The only usage cue is implicit in 'Check how much I have earned and what is pending.'

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

All New LLM Release Tracker — buy per-query in-session (llmwatch) tools Inspect

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

Need Help?