Skip to main content
Glama

prom_seller_list_payment_options

List available payment options for a seller on Prom.ua. Retrieve which payment methods a seller accepts before creating or configuring an order.

Instructions

List seller payment options.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses essentially nothing beyond the operation name. It does not state that this is a safe read-only call, whether results are scoped to the authenticated seller, whether the list is paginated, or what a payment option contains — all of which an agent must know to use it confidently.

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?

A single six-word sentence that front-loads the verb and resource with no filler. It is appropriately sized for a trivial enumeration tool, though it is so short that it is arguably under-specified rather than optimally concise.

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?

For a zero-parameter list tool with no output schema, the description should at least indicate what the returned options represent and how they are meant to be consumed. Instead it leaves the agent guessing about the return shape and the seller-account scoping, which is a modest but real gap.

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 schema is empty with 100% coverage, so there is nothing parameter-related for the description to add. Baseline for zero-parameter tools applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ("List") and resource ("seller payment options"), which is unambiguous and parallel to siblings like prom_seller_list_delivery_options and prom_seller_list_order_status_options. It does not explicitly distinguish itself from those siblings, but the resource noun alone is enough for an agent to pick correctly.

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?

There is no explicit when-to-use statement or named alternative, but the usage is strongly implied: it is a zero-parameter enumeration of available payment choices, presumably to feed a checkout or order flow. For a no-arg listing tool this is adequate, though a sentence like "call before creating an order to see accepted methods" would lift it.

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