Skip to main content
Glama

get-products

Retrieve all products added to the catalog so you can review or manage existing entries.

Instructions

Get all added products

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": "get-products"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and provides essentially none. "Get" implies a read-only operation, but nothing is said about return shape, pagination, result size, or what "added" actually means — all critical for a list tool 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single four-word phrase with zero waste and the scope qualifier is front-loaded, but its brevity comes from under-specification rather than tight editing. It is concise at the cost of saying almost nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is structurally simple (no params, no nested objects), which lowers the bar, but with no output schema and no annotations the agent still lacks any notion of what comes back or what "added" scopes. For a listing endpoint that is a meaningful gap.

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 schema to underspecify and no parameter meaning the description could add. Baseline 4 applies for a no-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase names a verb ("Get") and resource ("products") and the scope word "all" hints at a list operation, which loosely distinguishes it from get-product-by-id. However, "added products" is ambiguous — added by whom, to what (cart, catalog, watchlist)? — and the description never explicitly contrasts itself with the single-product and add-product siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite or exclusion, and no mention of the obvious alternative (get-product-by-id for a single item). An agent must infer that this is the list-everything variant purely from the word "all".

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