Review what the user currently has for sale. Use when they ask what they are selling, what their prices are, where their money goes, or want to check their listing before changing it. Returns the proxy URL, payout destination, commission rate and every listed tool with its price. 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 declare readOnlyHint and idempotentHint, so the safe-read nature is covered. The description adds context by outlining the exact return fields (proxy URL, payout destination, commission rate, listed tools with prices) and the prerequisite api_key from register_server. This is meaningful behavioral transparency beyond the annotations, though it doesn't cover errors or rate limits.
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 compact, using three sentences to cover purpose, use cases, return contents, and a prerequisite. It is front-loaded with the primary action and avoids redundant phrasing. No wasted words.
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?
With a single parameter and no output schema, the description adequately explains the tool's behavior and returns. It covers the key use cases and the required authentication context. The description is self-sufficient for an agent to select and invoke the tool 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 describes api_key as 'Your seller key' (100% coverage). The description enriches this by specifying that the key comes from register_server, which is a helpful source detail. Since the baseline for full schema coverage is 3, this additional context warrants a 4.
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 clearly identifies the tool as retrieving the user's current sales listing ('Review what the user currently has for sale'). It enumerates specific use cases and distinguishes it from sibling tools like set_tool_price by positioning it as a pre-change check. The verb+resource combination is specific and unambiguous.
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?
Explicitly states when to use the tool: when the user asks about what they're selling, prices, money destination, or before changing a listing. It implies not to use it for making changes, which differentiates from set_tool_price. However, it doesn't name sibling alternatives explicitly or state exclusions, so a 4 is appropriate.
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.