Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-getProducts

Read-onlyIdempotent

Retrieve the product catalog from Stripe to review available items and pricing. Use it to inspect product data needed for billing or subscription workflows.

Instructions

GET /stripe.getProducts

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": "stripe-getProducts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no disclosure of pagination behavior, result limits, whether it hits the live Stripe API (relevant given openWorldHint), or error behavior. It does not contradict the annotations, but it carries no informational weight on its own.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is a single route token with no waste but also no value — this is under-specification masquerading as brevity. There is no front-loaded explanation of what the call returns or when to reach for it.

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?

With no output schema and no parameter documentation, the description is the only channel for explaining the return shape and any pagination or filtering semantics, and it provides none. For a zero-arg, open-world list endpoint, an agent needs to know what comes back and whether results are complete or truncated.

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 no parameter semantics to explain; the baseline of 4 applies. The empty schema with additionalProperties=false is self-explanatory.

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

Purpose2/5

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

The description is just the raw route string "GET /stripe.getProducts", which restates the tool name rather than explaining it. An agent learns only that it is an HTTP GET against a Stripe products resource; it doesn't learn whether this lists all products, a single product, or what shape the result takes, and nothing distinguishes it from siblings like stripe-getCurrentPlan or stripe-getInvoices.

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 or when-not-to-use guidance, and no named alternative. The agent must infer from the name alone that this is the products catalog fetch versus plan/invoice/billing-status siblings.

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

Deploy Server

Other Tools