Skip to main content
Glama

ListMath: Marketplace Seller Fees

List marketplaces

list_marketplaces
Read-onlyIdempotent

List the supported US marketplaces with their valid categories, options, whether package dimensions are needed, the official fee pages used as sources and the date each was verified. Call this first to find valid category and option values.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: the scope is US-only, the data is reference-style with provenance (official fee pages as sources) and a per-entry verified date that signals freshness. It does not describe the response shape, but for a zero-parameter reference lookup that is a minor 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?

A single dense sentence lists the returned fields, followed by one short directive sentence on sequencing. Nothing is repeated from the title and every clause carries distinct information about what the agent will get back.

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?

There is no output schema, so the description carries the burden of describing return content and it does so by enumerating the fields and their provenance. It never states the structural format of the response, which is the only meaningful omission for a no-parameter tool of this complexity.

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, so the schema has nothing to explain and the baseline is 4. The description correctly adds no parameter discussion, and implicitly signals that no inputs are needed by framing it as a call-first discovery step.

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 opens with a specific verb and resource ('List the supported US marketplaces') and then enumerates exactly what each entry contains: valid categories, options, whether package dimensions are needed, official fee page sources, and verification dates. This clearly separates it from siblings like advise_marketplaces, compare_marketplaces, calculate_fees, and find_target_price, which all presume you already know the marketplaces and categories.

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?

'Call this first to find valid category and option values' gives explicit sequencing and a concrete reason to invoke it before other tools. It stops short of naming when a sibling should be used instead, so it is strong context rather than a full when/when-not rule.

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