Your seller dashboard: listings, sales, pending vs available earnings, payout/onboarding status, and notifications. Requires your seller api_key. Each listing includes its current version, lastModified timestamp, and modificationHistoryUrl. Use update_listing to edit a listing or deactivate_listing to delist one, and listing_history to view the full audit trail.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your vm_live_ API key |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description discloses the authentication requirement and the type of data returned, but it does not explicitly state that the operation is read-only or describe any side effects. Given the dashboard nature, this is acceptable but not fully transparent.
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 three sentences that efficiently cover purpose, requirements, and related actions. It front-loads the main contents. 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?
For a simple tool with one parameter and no output schema, the description sufficiently explains the return content and provides pointer to related tools. It could mention response format or pagination, but given the simplicity, it is adequate.
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 only parameter, api_key, is fully described in the schema (100% coverage). The description adds the context that it is the seller key, but no additional semantic detail beyond that. Baseline 3 applies because the schema carries the load.
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 this as the seller dashboard and enumerates its contents (listings, sales, earnings, payout/onboarding status, notifications). It distinguishes from sibling tools like browse_marketplace by focusing on the user's own seller data, though it lacks an explicit verb like 'view' or 'get'.
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?
It tells the user they need a seller api_key, and it directs them to update_listing, deactivate_listing, and listing_history for related actions, implicitly defining what this tool is for (viewing) versus those (editing/deleting/history). However, there is no explicit 'when not to use' statement.
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.
Most tools have clearly distinct purposes, but get_platform_stats and marketplace_stats overlap in the stats domain and could be confused. The rest are well-separated by buyer/seller/wallet roles.
Tool names mix verb-first patterns (buy_data, get_wallet_balance) with noun-first patterns (marketplace_stats, seller_dashboard, listing_history). The inconsistency is noticeable but still readable.
27 tools is above the heavy threshold and there are multiple near-duplicate stats tools and several informational/contact tools that could be consolidated. The scope is broad but the count feels excessive.
The tool set covers the full seller lifecycle (list, update, delist, dashboard), buyer lifecycle (browse, preview, buy, get receipt, rate), wallet management, and health-data-specific flows. Missing refund/dispute tools are a minor gap.
