VIA Network: Agentic Commerce

counter_quote

Counter an existing quote, forwarded to the owning seller. Pass the quote_ref and a target price, revised selections, or both. Appends a round to the negotiation; stays non-binding until the seller approves.

Input Schema

TableJSON Schema

Name	Required	Description
`note`	No	Free-form message to the seller.
`quote_ref`	Yes
`selections`	No	Revised configuration, if you are changing what you want.
`seller_mcp_url`	Yes	mcp_ref.seller_mcp_url from a discovery result.
`counter_total_usdc`	No	Your proposed price for the configuration.

Schema Changelog

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

First observedJul 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description bears the full burden. It discloses that the action forwards to the seller, appends a round, and remains non-binding. It does not cover authentication or rate limits, but the core behavioral traits are well communicated.

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?

Three sentences: first sentence states purpose and direction, second lists key parameters, third explains behavior. Front-loaded with no wasted words.

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

Completeness4/5

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

For a tool with 5 parameters, nested objects, and no output schema, the description covers purpose, usage, and behavioral outcome. It could mention prerequisites (e.g., existing quote) and return format, but overall is adequate.

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 coverage is high (80%). The description adds usage context beyond the schema: 'Pass the quote_ref and a target price, revised selections, or both.' However, 'note' and 'seller_mcp_url' are not described in the description, leaving some gaps.

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?

Description clearly states 'Counter an existing quote, forwarded to the owning seller.' It specifies the action (counter), resource (quote), and direction (to seller). This distinguishes it from siblings like accept_offer or request_quote.

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

Usage Guidelines4/5

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

Description explains when to use: 'Pass the quote_ref and a target price, revised selections, or both.' It also clarifies outcome: 'Appends a round to the negotiation; stays non-binding until the seller approves.' However, it lacks explicit exclusions or comparisons to alternatives.

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?