Skip to main content
Glama

prom_seller_list_clients

List clients for the authenticated Prom.ua seller account, using limit and last_id to page through records.

Instructions

List clients of the authenticated Prom.ua seller company.

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_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records requested from Prom.ua.
last_idNoProm.ua cursor/id for pagination where supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.9/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 full behavioral burden. It notes the 'authenticated' seller context, but says nothing about pagination behavior (the schema has a cursor param), rate limits, or what the returned client records contain—significant gaps for a tool with zero annotation coverage.

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 tight sentence with no filler; the scope qualifier ('authenticated seller company') is front-loaded. There is simply little content to structure around.

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 simple two-optional-param read tool with no output schema this is minimally adequate, but it omits how pagination via last_id should be exercised and how it relates to the singular client-getter sibling. Nothing an agent needs is fatally missing, yet little is added.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both params (limit, last_id) are already documented in the schema. The description adds no syntax or usage detail beyond it, so the baseline 3 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?

States a specific verb (list) and resource (clients) scoped to 'the authenticated Prom.ua seller company'. An agent can distinguish it from prom_seller_get_client by the plural 'list', but the description never names or contrasts with that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative prom_seller_get_client for fetching a single client or how this differs from other list tools. Usage is only inferable from the name.

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