Skip to main content
Glama
Sign In
agent-pay-gate

agent-pay-gate

by NariP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

List products

list_products

Retrieve Slow Morning Coffee’s product catalog with SKUs and USD prices to support quotes and review orders before PayPal payment approval.

Instructions

List what Slow Morning Coffee sells, with SKUs and prices in USD.

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 observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'List' signals a read-only operation and it discloses the returned fields and currency, which is useful. It says nothing about result size, whether the full catalog is always returned, ordering, or whether inactive/discontinued items are included.

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?

One sentence, front-loaded with the action and the key content the agent needs (SKUs, USD prices). Nothing redundant or padded.

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 does the essential work of saying what the result contains. Slight gap: it doesn't say whether the list is the complete catalog or how large it typically is, which matters for an agent planning follow-up calls.

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 zero parameters, so there is no parameter ambiguity to resolve; baseline applies. The description correctly frames the call as unfiltered and complete rather than implying hidden options.

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 ('what Slow Morning Coffee sells') plus the fields returned (SKUs, prices in USD). An agent knows exactly what comes back. It does not name or distinguish any sibling, though the siblings (check_payment, create_quote, request_payment) operate in a different domain, so ambiguity is low.

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 catalog lookup for product/SKU/price data. There is no explicit when-to-use statement, no mention of whether this is the authoritative source for pricing before calling create_quote, and no exclusions.

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

Deploy Server

Other Tools