VIA Network: Agentic Commerce

get_product

Fetch full detail for ONE listing before buying, from anywhere on the network, without leaving this connector. Pass the seller_mcp_url and product_id exactly as they appear in a find_seller / get_seller_products result (mcp_ref.seller_mcp_url and mcp_ref.product_id). Returns the listing with price, stock, and what the purchase requires. This forwards to the owning seller; the same buy loop (get_product -> get_shipping_quote -> buy_product) then settles here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product_id`	Yes	The listing id from discovery (mcp_ref.product_id).
`seller_mcp_url`	Yes	mcp_ref.seller_mcp_url from a find_seller / get_seller_products result.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 27, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that the tool forwards to the owning seller (network call) and that it returns price, stock, and purchase requirements. No annotations existed, so description fully covers behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with critical information front-loaded. First sentence states core purpose, second gives parameter guidance and return info, third explains forwarding and buy loop. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description fully explains the tool's role in a multi-step buy flow, parameter provenance, and what the response contains. Complete for a single-listing detail fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds value by specifying the exact source of the parameter values (mcp_ref.seller_mcp_url and mcp_ref.product_id from discovery results), which is not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Fetch' and resource 'full detail for ONE listing', clearly distinguishing it from sibling tools like find_seller or get_seller_products by focusing on purchase intent. It also positions itself within a buying workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('before buying'), how to pass parameters ('exactly as they appear in find_seller / get_seller_products result'), and places the tool in a sequence (get_product -> get_shipping_quote -> buy_product). Provides both usage context and alternative steps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All VIA Network: Agentic Commerce tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (discovery, purchasing, negotiation, seller management, taste/intent). Some overlap exists, e.g., multiple ways to get product details, but descriptions clarify distinct use cases. A few tools like find_buyers and get_buyer_briefs might be confused at first glance but have different inputs.

Naming Consistency4/5

Tool names predominantly follow verb_noun pattern in snake_case, e.g., find_seller, buy_product, get_shipping_quote. The outlier is seller_mcp_url which starts with a noun instead of a verb, and negotiate is a bare verb but fits. Overall consistent with minor deviations.

Tool Count3/5

28 tools is on the high side for a single server, but the domain is complex (agentic commerce covering discovery, purchasing, negotiation, seller registration, etc.). The count is borderline heavy but reasonable for the breadth of functionality.

Completeness4/5

The tool set covers major aspects of agentic commerce: search, buying, negotiation, shipping, digital delivery, seller onboarding, and taste/intent. Missing features like order tracking or store updates are minor gaps; core workflows are well-supported.

Resources

Need Help?