List active sellers across the VIA network (VIA app + RRG + integrated platforms). Each result is tagged with its platform and includes the per-seller MCP URL to connect to for deeper interaction (list_products, ask_sales_agent, buy_product).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Optional cap on results. Omit to enumerate the ENTIRE network (no limit), which is the default. | |
| category | No | Optional kind filter (applies to VIA-app sellers only). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Implies read-only behavior through 'List', but does not explicitly state that the operation is safe, idempotent, or free of side effects. Also does not mention authentication 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?
Two sentences, no fluff. Front-loaded with purpose and scope, immediately followed by key output details. Every sentence earns its place.
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 2 optional parameters and no output schema, the description covers the primary purpose, output structure (platform tag and MCP URL), and links to further tools. Could benefit from listing all fields in the result, but overall sufficient for selection and invocation.
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?
Input schema has 100% coverage, but description adds value: clarifies that 'category' applies only to VIA-app sellers and that omitting 'limit' enumerates entire network. This extra context improves understanding beyond the schema.
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?
Clearly states the verb 'List' and resource 'active sellers' with specific scope 'across the VIA network (VIA app + RRG + integrated platforms)'. Distinguishes from sibling tools like 'find_seller' which searches for a specific seller, and 'get_seller_products' which is more specific.
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?
Provides clear context for use: listing all active sellers. Mentions that results include MCP URLs for deeper interaction, guiding subsequent tool use. However, lacks explicit exclusion criteria or when not to use it.
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.
