Skip to main content
Glama

silex_check_agent_earnings

Read-onlyIdempotent

Check live unlocks sold, gross USD earned, and 1% fee ledger for your *.withsilex.com agent subdomain.

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": {
      "wallet": "<wallet>"
    },
    "name": "silex_check_agent_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoOptional *.withsilex.com agent subdomain handle to inspect.
walletYesCreator Nano ($XNO) payout address (nano_1... or nano_3...) to query unlocks sold and gross USD earned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / handle / description
      Added value: +"Optional *.withsilex.com agent subdomain handle to inspect."
    • addedInput schema / properties / wallet / description
      Added value: +"Creator Nano ($XNO) payout address (nano_1... or nano_3...) to query unlocks sold and gross USD earned."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds real value by enumerating what is returned (unlocks sold, gross USD, 1% fee ledger), but says nothing about whether the handle defaults to the caller's own subdomain, authorization requirements, or result freshness.

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?

A single front-loaded sentence with zero filler: the resource being queried and the scope appear immediately. Nothing is repeated from the schema or annotations.

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 only two parameters, full schema coverage, and annotations carrying the safety profile, the main remaining burden is telling the agent what data comes back — which the description does by naming the three ledger metrics in the absence of an output schema. Only the optional-handle default behavior is left unexplained.

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 description coverage is 100%, so the baseline is 3; both the wallet (nano_1.../nano_3...) and handle parameters are already documented in structured fields. The description adds no meaning beyond that, notably never explaining how handle and wallet combine or what an omitted handle implies.

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 concrete verb ('Check') and three named resources (live unlocks sold, gross USD earned, 1% fee ledger) scoped to a *.withsilex.com agent subdomain. An agent can tell this is an earnings/ledger lookup, not a mint or paywall mutation like silex_mint_agent_paywall. It stops short of explicitly contrasting with any sibling, but the domain 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 only implied: the phrase 'for your *.withsilex.com agent subdomain' tells the agent the context in which it applies, but there is no explicit when-to-use, no prerequisites, and no named alternative for related tasks. An agent can guess this is the read-side counterpart to minting, but must infer it.

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.