Skip to main content
Glama

List products

list_products

The Aruon Beacon products offered today, with their prices in US dollars before tax (5% Texas sales tax on SaaS is added at checkout), each orderable one's crypto total, and the payment rails accepted now. Other products are quoted by a person: see https://beacon.aruon.ai/pricing.json.

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.6/5.0
Behavior3/5

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

No annotations exist, so the description bears the full burden. It does disclose meaningful behavior about the payload: prices are pre-tax, a 5% Texas SaaS tax is applied at checkout, crypto totals are per orderable item, and payment rails are 'accepted now' (implying time-sensitivity). It does not state that the call is read-only, whether results are cached or dated, or any auth/rate-limit facts.

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?

It is a single dense sentence plus a short pointer URL, with no filler or repetition. The pricing/tax detail is packed tightly and the single sentence carries several clauses, which slightly slows scanning but every clause conveys caller-relevant information.

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?

With no output schema, the description must characterize the return value, and it does: item prices, tax treatment, crypto totals, and payment rails — enough for an agent to decide whether the response answers its question. Gaps remain around the shape of the result (fields, per-item vs per-rail structure) and what 'today' means for freshness, but the core is covered.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly adds no pseudo-parameter guidance that would conflict with the empty schema.

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 specific resource ('Aruon Beacon products offered today') and enumerates exactly what the listing conveys: USD prices before tax, crypto totals, and accepted payment rails. The listing verb is carried only by the name/title, and no sibling tool (check_coverage, create_order, get_order_status) is named, so it is clear but not differentiated.

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?

There is one useful scope exclusion — 'Other products are quoted by a person' points to a human/URL path instead of this tool — which tells the agent when this tool is insufficient. However, there is no explicit when-to-use framing relative to create_order (e.g., 'use this to find product IDs before ordering') and no prerequisites stated.

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