Report how much the user has earned selling their tools. Use when they ask about sales, revenue, income, how much they made, how many calls were paid, or which tool sells best. Returns paid calls, gross revenue, commission and net revenue, broken down per tool. Requires the api_key from register_server.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your seller key. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint, and the description adds context beyond that by detailing the output (paid calls, gross revenue, commission, net revenue per tool) and noting the api_key must come from register_server. This is useful behavioral information without contradicting the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main purpose, and every sentence provides actionable value: what it reports, when to use it, and what it returns. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (1 parameter, no output schema, read-only semantics), the description is complete: it covers purpose, usage triggers, return contents, and required key provenance. No additional context is necessary for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers the single parameter with 100% coverage ('Your seller key'), so the baseline is 3. The description adds meaning by specifying the api_key is specifically from register_server, which is a helpful cross-reference beyond the schema's generic description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Report how much the user has earned selling their tools.' It clearly distinguishes itself from siblings by focusing on earnings and explicitly lists the returned metrics (paid calls, gross revenue, commission, net revenue).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists when to use this tool (when they ask about sales, revenue, income, how much they made, how many calls were paid, or which tool sells best), providing clear usage context. It does not explicitly mention when not to use or name alternatives, so it does not fully meet the 'explicit alternatives' bar for a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: earnings retrieval, listing review, marketplace browsing, server registration, price updates, and ownership verification. No two tools have overlapping purposes, making misselection unlikely.
All tool names follow a consistent verb_noun pattern in snake_case (get_earnings, list_registered_servers, set_tool_price). The style is uniform and predictable.
At 6 tools, the set is well-scoped for a monetization gateway covering both seller and buyer workflows. Each tool serves a necessary function without bloat or excessive granularity.
Core seller workflows are covered: register, price, view listing, view earnings, verify. Buyer browsing is also covered. Minor gaps exist, such as no tool to unregister a server or update payout destination, but these are workarounds and not fatal.