Skip to main content
Glama
iaptic

Iaptic MCP Server

Official
by iaptic

stripe_prices

Retrieve Stripe products and their associated prices, including subscription terms and metadata. Results are cached for 5 minutes.

Instructions

Get available Stripe products and prices.

  • Returns list of products with their associated prices

  • Each product includes:

    • Product ID and display name

    • Description and metadata

    • Available pricing offers

    • Subscription terms if applicable

  • Results are cached for 5 minutes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'stripe_prices' - calls this.api.getStripePrices() and returns JSON content.
    case 'stripe_prices':
      const prices = await this.api.getStripePrices();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(prices, null, 2)
        }]
      };
  • The tool registration and input schema for 'stripe_prices' - defines name, description, and input parameters.
          {
            name: "stripe_prices",
            description: `Get available Stripe products and prices.
    - Returns list of products with their associated prices
    - Each product includes:
      - Product ID and display name
      - Description and metadata
      - Available pricing offers
      - Subscription terms if applicable
    - Results are cached for 5 minutes${appNameRequired ? '\n- Requires appName parameter when using master key' : ''}`,
            inputSchema: {
              type: "object",
              properties: {
                ...(appNameRequired ? {
                  appName: {
                    type: "string",
                    description: "Name of the app to fetch data from. Required when using master key."
                  }
                } : {})
              },
              required: appNameRequired ? ["appName"] : undefined
            }
          }
  • src/server.ts:70-82 (registration)
    Tool registration via ListToolsRequestSchema - collects tools from all tool classes including StripeTools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          ...this.tools.customers.getTools(),
          ...this.tools.purchases.getTools(),
          ...this.tools.transactions.getTools(),
          ...this.tools.statistics.getTools(),
          ...this.tools.stripe.getTools(),
          ...this.tools.events.getTools(),
          ...this.tools.app.getTools()
        ]
      };
    });
  • src/server.ts:102-104 (registration)
    Routing stripe_* tool calls to the StripeTools handler, including stripe_prices.
    if (name.startsWith('stripe_')) {
      return await this.tools.stripe.handleTool(name, args);
    }
  • The underlying API helper that makes the HTTP GET request to /stripe/prices endpoint.
    async getStripePrices() {
      const response = await this.client.get('/stripe/prices');
      return response.data;
    }
Behavior4/5

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

The description discloses caching behavior (5-minute cache) and lists the return structure. Since no annotations exist, the description carries full burden; it provides useful behavioral insight but could mention authentication requirements or data freshness.

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

Conciseness5/5

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

The description is concise, with a clear main sentence and bullet points for details. Every sentence adds value, and it is well-structured for quick scanning.

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

Completeness5/5

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

Given zero parameters and no output schema, the description fully explains what the tool returns and includes additional context (caching). It is complete for the tool's purpose.

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 input schema has zero parameters with 100% coverage, so the description does not need to add parameter guidance. Baseline 4 is appropriate.

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

Purpose5/5

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

The description clearly states the tool 'Get available Stripe products and prices' with a specific verb and resource, and distinguishes from siblings by focusing on price/product listing, which no other sibling does.

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 tool versus alternatives; it does not mention exclusions or prerequisites. The description only states what it does without providing context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iaptic/mcp-server-iaptic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server