Skip to main content
Glama

Ace Website MCP

list_products

Read-onlyIdempotent

Everything an agent can buy from Ace, with Stripe-verified prices, billing terms, delivery and live availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the description does not need to repeat it. The description does add content-level context that no annotation provides: prices are Stripe-verified and results include billing terms, delivery and live availability. It says nothing about result size, pagination, ordering, or whether the catalog is fetched live, which matters for an open-world read with no output schema.

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 dense sentence with zero wasted words, and the scope ('everything an agent can buy from Ace') is front-loaded followed by the differentiating field list. It is a fragment rather than a complete sentence, but nothing is padded or repeated.

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 zero-parameter read tool with no output schema, the description carries the burden of explaining what comes back, and it does so by enumerating prices, billing terms, delivery and live availability. Remaining gaps are minor: no indication of currency/price format, result volume, or whether availability is real-time versus cached.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. However, the description never states that the call is unfiltered and returns the entire catalog in one shot, which is the one semantic point a no-param listing should make explicit; that omission pulls it down slightly.

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 identifies the exact resource: everything an agent can buy from Ace, i.e. a purchasable product catalog, and names the fields it carries (Stripe-verified prices, billing terms, delivery, availability). It is clearly distinct from the checkout- and page-oriented siblings. It lacks an explicit verb, reading as a noun phrase rather than 'Lists products', which keeps it just short of a 5.

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?

Usage is only implied: an agent would infer it browses the catalog before calling create_checkout, and the phrase 'everything an agent can buy' suggests it is the entry point for purchasing decisions. There is no explicit statement of when to call it versus siblings, no mention of prerequisites or that it takes no filters.

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