VIA Network: Agentic Commerce

accept_offer

Ask a buyer's Buying Agent to accept a negotiated offer, forwarded to their buyer MCP. The agent auto-accepts only within the buyer's delegation caps, otherwise it queues the offer for the buyer's approval.

Input Schema

TableJSON Schema

Name	Required	Description
`category`	No	Product category, checked against the buyer's lists.
`offer_id`	Yes	Your reference id for the offer being accepted.
`amount_usd`	No	Total order amount in USD, for the caps check.
`buyer_mcp_url`	Yes	The buyer's mcp_url from a find_buyers result.

Schema Changelog

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

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: forwarding to buyer MCP, auto-accepting within delegation caps, and queuing for approval otherwise. 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.

Conciseness5/5

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

The description is two sentences (25 words), concise and front-loaded with the main action. Every sentence adds value with no fluff.

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

Completeness3/5

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

While the description explains the auto-accept/queue behavior well, it lacks information about the return value or what the agent can expect as a response. Given no output schema, the description should cover this gap.

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

Parameters3/5

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

Schema coverage is 100% with each parameter having a description. The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states the tool's function: asking a buyer's Buying Agent to accept a negotiated offer. It specifies the resource (buyer's Buying Agent) and action, distinguishing it from sibling tools like negotiate or counter_quote.

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

Usage Guidelines3/5

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

The description implies usage after negotiation but does not explicitly provide when-to-use or when-not-to-use guidance. It does not mention alternatives or conditions for choosing this tool over siblings.

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?