Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stripe_products

Read-onlyIdempotent

Retrieve and list Stripe products using a secret key, with optional filters for active status, result limit, and pagination via starting_after.

Instructions

List Stripe products.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "secret_key": "<secret_key>"
    },
    "name": "stripe_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
activeNo
secret_keyYes
starting_afterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and mutability profile is fully covered. The description adds nothing beyond that — no mention of pagination behavior, result limits, or authentication expectations for a list endpoint that needs a secret_key.

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?

A single four-word sentence with zero waste, but the brevity is under-specification rather than disciplined concision given the undocumented parameters.

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?

For a four-parameter listing tool with a required credential and no output schema, the description leaves the agent without pagination, filtering, or return-shape context. It is not sufficient to invoke the tool confidently beyond the default call.

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%, so the description carries the full burden for four parameters. It says nothing about what 'active' filters, what 'limit' caps, or that 'starting_after' is a pagination cursor — exactly the semantics an agent needs to enumerate results correctly.

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?

States a specific verb (List) and resource (Stripe products), which is enough to distinguish it from the algorithmic/log tools in the sibling set. However, it does nothing to distinguish it from the adjacent stripe_invoices, stripe_prices, and stripe_charges tools beyond the noun itself.

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?

No guidance on when to use this versus stripe_prices, stripe_invoices, or the numerous other Stripe siblings, and no mention of prerequisites such as API key scope. The agent must infer everything from the noun.

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