Skip to main content
Glama

Sunset Website MCP

list_products

Read-onlyIdempotent

Everything an agent can buy from Sunset, 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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description only needs to add context. It does so meaningfully by stating that prices are Stripe-verified and that availability is live, which tells the agent the data is authoritative and time-sensitive rather than cached. It stops short of describing result size, pagination, or ordering.

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?

One dense sentence with no filler, and the scope ('everything an agent can buy') is front-loaded before the payload details. The phrasing 'Everything an agent can buy' is slightly roundabout where 'products' would be sharper, but nothing is wasted.

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?

With zero parameters and no output schema, the description's only real job is to convey what comes back, and it enumerates the key returned facets: verified price, billing terms, delivery, and live availability. That is sufficient for an agent to decide to call it and to interpret the response.

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 there is nothing for the description to disambiguate beyond noting the absence of filters. Baseline for a zero-parameter tool applies; the description correctly does not invent filtering semantics.

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 names the resource ('everything an agent can buy from Sunset') and the payload's substance (prices, billing terms, delivery, availability), so an agent can tell this is the product catalog read. It is distinguishable from sibling tools like create_checkout and read_page, though the action verb is left implicit and only recovered from the tool name.

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 can infer this is the discovery step preceding create_checkout or get_checkout, but the description never says when to call it, whether it should be called first, or what to do if a product is missing. No alternatives are named or excluded.

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