Skip to main content
Glama

Fixed-price products

list_products
Read-only

The fixed-price MDJ products with their USD prices and store page links (trip kick-off deposit, planning, apps, experience maps). Ground services are not listed: they are priced by quote only.

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
typeNoOptional filter by product type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by disclosing the return contents (USD prices and store page links) and the catalog boundary, which matters because there is no output schema. It says nothing about ordering, pagination, or whether the full catalog is always returned when unfiltered.

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?

Two short sentences, zero filler, with the core offering stated first and the exclusion stated second. Every clause carries information an agent needs.

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 single-optional-parameter read tool with no output schema, the description covers what is returned and what is out of scope. The remaining gap is minor: it does not state that an unfiltered call returns all product types.

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?

Schema description coverage is 100% and the enum is fully described, so the baseline is 3. The parenthetical product list loosely maps to the enum values (deposit, planning, app, map), but 'guide' is not clearly accounted for and the description adds no filtering semantics beyond the 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 concrete resource (fixed-price MDJ products) and what comes back with each item (USD prices, store page links), plus a parenthetical enumeration of the catalog. It does not name a sibling tool by contrast, but the explicit exclusion of ground services establishes a scope boundary an agent can use.

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?

It clearly states a when-not condition: ground services are not listed because they are quote-priced, which routes the agent away from this tool for those items. It gives no positive trigger condition and names no alternative tool (e.g., estimate_trip) for the quote case, so the routing is implied rather than complete.

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