Skip to main content
Glama

List the products Polargate makes

list_products

Products Polargate makes and owns, as opposed to work for clients. PolarRabbit is a free Mac app.

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
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that results are owned products (not client projects) and gives one concrete example (PolarRabbit, a free Mac app), but says nothing about ordering, completeness, or whether the list is filtered by locale.

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?

Two short sentences with the scoping statement front-loaded. The second sentence ('PolarRabbit is a free Mac app') is illustrative rather than essential, but it costs little and grounds the abstract scope.

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

Completeness3/5

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

For a simple optional-param list tool with no output schema, the description should at least characterize the return items (names, links, pricing?) and clarify the locale effect. It defines scope but leaves what an agent actually gets back underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single optional 'locale' parameter (enum en/es/nl), and the description never mentions it. An agent gets no signal about what locale changes—product name language presumably, but that is inference.

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 states the resource clearly: products that Polargate makes and owns, explicitly distinguished from client work. The verb is only implied by the tool name, but an agent can tell what this returns vs. the service-oriented siblings such as list_services.

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?

The phrase 'as opposed to work for clients' implicitly routes the agent away from list_services, which is useful, but there is no explicit when-to-use instruction or mention of alternatives like get_pricing or how_to_start for the same subject matter.

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