Skip to main content
Glama

Products Provkeep reads rules for

list_products
Read-onlyIdempotent

Lists every peptide and compounded drug Provkeep reads rules for, with the other names each one is matched by. Does not count as a lookup.

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.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description's main added value is the accounting note that the call "does not count as a lookup" — a real quota/usage trait an agent cannot see in structured fields. It also discloses that alias names are returned, which matters since there is 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.

Conciseness4/5

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

Two short sentences with the core scope front-loaded and no padding. The trailing "Does not count as a lookup" is useful but slightly cryptic out of context, since "lookup" is an unexplained term that overlaps with the sibling tool name lookup_rules.

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 parameters, no output schema, and strong annotations, the description covers what an agent needs: the scope of the list, that aliases come back with each entry, and that the call is not metered as a lookup. Only minor gaps remain, such as whether results are ordered or paginated and how large the catalog typically is.

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; the baseline of 4 applies. The description correctly presents this as a full-catalog list with no filtering inputs.

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?

Uses a specific verb ("Lists") plus a concrete resource ("every peptide and compounded drug Provkeep reads rules for") and states what each entry includes (alternative matched names). It implicitly separates itself from lookup_rules via "Does not count as a lookup," though it never names the sibling that lists watched products.

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: the phrase "Does not count as a lookup" suggests this is the free, non-consuming call to make when enumerating the product catalog rather than querying rules. There is no explicit when-to-use or when-not guidance, and no direction on choosing between this and list_watched_products.

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