Skip to main content
Glama

x402 payment requirements + pay URL for a paid Avasis route

avasis_quote
Read-onlyIdempotent

Return the x402 payment requirements (price, accepts[] with amount/asset/payTo/network) and pay URL of token-verdict, wallet-risk or research-pack so YOUR OWN x402 wallet can pay the HTTP route. Omit product to list the keys. This server never holds or spends funds. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "avasis_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNoe.g. {"chain": "base", "token": "0x..."}
productNofocusVerdict | focusWallet | focusResearch (or the slug: token-verdict, wallet-risk, research-pack)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description adds important behavioral context: 'This server never holds or spends funds. Free.' It does not cover rate limits or pay-URL expiration, but the fund-handling disclosure is a key addition.

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 front-loaded with the return value, then usage hints, then safety context. It is four short sentences with no wasted words; the parenthetical return-field list and 'Free' are both useful.

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 no output schema, the description adequately outlines the return structure (price, accepts[] with amount/asset/payTo/network) and the pay URL. Combined with annotations covering safety and idempotence, an agent has enough to call it correctly, though it could mention error or edge cases.

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?

With schema coverage at 100%, the baseline is 3. The description adds meaning by specifying 'Omit product to list the keys' (clarifying the effect of the optional product parameter) and by mapping product values to actual slugs (token-verdict, wallet-risk, research-pack). The 'input' object is not elaborated beyond the schema example.

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 states a specific verb ('Return') and resource ('x402 payment requirements ... and pay URL'), enumerates the returned fields (price, accepts[] with amount/asset/payTo/network), and names the three products (token-verdict, wallet-risk, research-pack). This is enough to distinguish it from the sibling product tools.

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?

It gives clear context for use: 'so YOUR OWN x402 wallet can pay the HTTP route' and 'Omit product to list the keys.' It does not explicitly state when not to use this tool or name alternatives, but the context is sufficiently clear for an agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources