Skip to main content
Glama

Payment options

payment_options
Read-onlyIdempotent

List the crypto assets and chains a buyer can pay with on Port66 (for example BTC on Bitcoin, SOL on Solana, ETH or USDC on Ethereum, Arbitrum or Base). Payments go through NEAR Intents and the seller always receives the exact price in USDC. Returns available (whether cross-chain payment is switched on) and assets, each with a symbol and chain to use as pay_with and chain in price_in_crypto. Takes no input.

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": "payment_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: payments route through NEAR Intents and the seller always receives the exact price in USDC, plus the meaning of the available flag and the shape of the assets list. It omits whether the result is static/cacheable or how often the asset set changes, which is the only notable gap.

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?

Four short sentences, front-loaded with the purpose, then mechanics, then return shape, then the no-input note. The asset examples are the only elaboration, and they usefully bound the scope rather than padding.

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?

There is no output schema, and the description compensates by naming the returned fields (available, assets with symbol and chain) and how they are consumed downstream. For a zero-parameter read tool with annotations covering safety, nothing an agent needs to call it correctly is missing.

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 no parameters, and the description explicitly confirms 'Takes no input', leaving nothing ambiguous. It also documents the response fields the agent must map to other tools' parameters, which is extra value beyond the empty schema.

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 opening sentence names a specific verb and resource ('List the crypto assets and chains a buyer can pay with') and scopes it to Port66, with concrete examples (BTC on Bitcoin, SOL on Solana) that make the resource unambiguous. It also signals the downstream consumer, so an agent can tell this apart from price_in_crypto, get_listing, or search_listings.

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 states the operative use case clearly: the returned symbol and chain are meant to be passed as pay_with and chain to price_in_crypto, which effectively routes the agent to the correct next step. It does not spell out explicit exclusions or failure conditions (e.g., what to do when available is false), so it stops short of full when/when-not guidance.

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