VIA Network: Agentic Commerce

claim_pass

Claim a FREE entry pass to an event on the VIA network, directly from discovery. FREE guest-list tiers only (price 0, the kind find_seller / get_seller_products surface at $0). No payment, no wallet, no x402: provide the attendee name and email, and VIA records the place, emails a confirmation, and notifies the organiser. One pass per email / per account. Paid products are NOT claimable here: connect to the seller's per-seller MCP and use buy_product (USDC via x402). Pass the product_id from a find_seller result (mcp_ref.product_id) or get_seller_products.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Name of the person attending, for the guest list.
`email`	Yes	Email to confirm the place to and for the organiser to admit by.
`product_id`	Yes	UUID of the free pass tier, from a find_seller / get_seller_products result.
`buyer_wallet`	No	Optional Base wallet, if the claimer has a VIA buyer identity.
`buyer_agent_id`	No	Optional ERC-8004 agent id of the agent claiming on the buyer's behalf.

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?

No annotations provided, but description fully discloses behavior: no payment, no wallet, emails confirmation, notifies organizer, one pass per email/account. 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?

Single well-structured paragraph with front-loaded main action. Every sentence adds value—no fluff, no repetition.

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 lacking output schema, description explains what happens (records place, emails, notifies organizer) and constraints (one per email/account, free only). Parameters are fully documented. Complete for a 5-param 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 covers all parameters with descriptions. Description adds context: source of product_id from find_seller/get_seller_products, and explains optional nature of buyer_wallet and buyer_agent_id.

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?

Clearly states 'Claim a FREE entry pass' with specific verb and resource. Distinguishes from sibling tools like 'buy_product' by explicitly stating that this tool is for free passes only.

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 (free tiers with price 0) and when not to use (paid products), providing a direct alternative: 'use buy_product (USDC via x402)'. No ambiguity.

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?