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, openWorldHint false, and idempotentHint, so safety is covered. The description adds valuable behavioral context beyond annotations by specifying the exact return payload (proxy URL, payout destination, commission rate, listed tools with prices) and the api_key requirement. No contradictions.
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?
Two sentences, front-loaded with purpose, and every clause adds value. No redundant filler or repetition of schema content.
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?
For a simple read-only tool with one parameter and no output schema, the description fully covers what it does, when to use it, what it returns, and the key requirement. Sibling tools are sufficiently differentiated, and no additional details seem necessary.
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?
Schema coverage is 100% with 'Your seller key.' The description enriches this by stating the key must come from register_server and explicitly says 'Requires' it, which adds provenance and usage nuance. However, schema lists required as 0, so there is a slight inconsistency, but the description's instruction is still helpful.
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 states the tool reviews the user's current for-sale listing, with a specific verb and resource. It distinguishes from siblings by focusing on the listing contents (prices, payout destination, commission rate) rather than earnings or server registration.
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 provides when-to-use scenarios: 'when they ask what they are selling, what their prices are, where their money goes, or want to check their listing before changing it.' Also gives a prerequisite (api_key from register_server), which helps guide correct invocation.
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 has a clearly distinct purpose: earnings reporting, listing review, marketplace browsing, server registration, pricing changes, and ownership verification. There is no overlap between these operations, so an agent will not confuse them.
All tool names follow a consistent verb_noun pattern: get_earnings, get_my_listing, list_registered_servers, register_server, set_tool_price, verify_ownership. The style is uniform and predictable, making it easy to infer what each tool does.
Six tools is well-scoped for a payment and marketplace server. Each tool earns its place by covering a distinct aspect of the seller workflow without unnecessary bloat.
The tool surface covers the full lifecycle for sellers: registering a server, managing prices, viewing earnings, reviewing listing, and verifying ownership. There are no obvious dead ends or missing core operations for the stated purpose.