Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice x402 Top-up Requirements

venice_x402_top_up_info
Read-onlyIdempotent

Fetch x402 top-up payment requirements, including accepted USDC options, networks, receiver wallets, minimum amounts, and settlement timeout, without charging or authentication.

Instructions

Fetch the x402 top-up payment requirements: the accepted USDC payment options (currently Base and Solana), each with network, asset, receiver wallet (payTo), minimum amount in base units, and settlement timeout. Sends an empty POST with no payment header, so nothing is charged. Signing and PAYMENT-SIGNATURE submission happen OUTSIDE this MCP server. No authentication required.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / amount_usd
      Removed value: -{
-  "maximum": 1000000,
-  "minimum": 1,
-  "type": "number"
-}
    • removedInput schema / properties / wallet_address
      Removed value: -{
-  "pattern": "^0x[a-fA-F0-9]{40}$",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "wallet_address"
-]
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds several things they cannot: it is an empty POST with no payment header, nothing is charged, no authentication is required, and signing occurs outside this server. That goes well beyond the safety profile.

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

Conciseness4/5

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

Front-loaded with the core action and purpose, then the return fields, then the behavioral caveats. Every sentence carries information; only the parenthetical field list makes it slightly dense, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing the response and does so fully (accepted USDC options, Base/Solana, payTo, minimum base units, settlement timeout). An agent has everything needed to call and interpret it.

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?

The tool takes zero parameters, so per the calibration the baseline is 4. There is nothing further for the description to disambiguate.

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?

States a specific verb (Fetch) and resource (x402 top-up payment requirements) and enumerates the exact payload fields returned (network, asset, payTo, minimum amount, settlement timeout). The agent can distinguish it from venice_x402_balance and venice_x402_transactions without opening any schema.

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?

Frames the call as the discovery step before payment and clarifies that signing/PAYMENT-SIGNATURE submission happens outside the MCP server, which tells the agent where this tool's responsibility ends. It does not explicitly name an alternative or exclusion, so it falls just short of a 5.

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

Deploy Server

Other Tools