Skip to main content
Glama
Sign In
leximo-ai-call-assistant-mcp-server

leximo-ai-call-assistant-mcp-server

Official
by Leximo-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_checkout_session

Creates a Stripe checkout session to subscribe a user to a plan and returns a payment URL.

Instructions

Create a Stripe checkout session to subscribe to a plan. Returns a URL the user should open in their browser to complete payment.

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": {
      "priceId": "<priceId>"
    },
    "name": "create_checkout_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceIdYesStripe price ID from the get_plans tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.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 full burden. It states it creates a session and returns a URL, which implies a mutation. However, it doesn't disclose potential side effects, rate limits, or session expiration, making it minimally adequate.

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?

Two short sentences, each earning its place. No fluff.

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 one required parameter and a simple return value (URL), the description covers the essential information: what it does, what input is needed, and what output to expect. It lacks details like error cases or timeouts, but overall complete for its simplicity.

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?

Schema coverage is 100% with a description for priceId. The description adds value by noting the priceId comes from get_plans, providing context beyond the schema.

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's action (create a Stripe checkout session) and its purpose (to subscribe to a plan). It also explains the return value (URL for payment). It distinguishes from siblings like get_plans and get_subscription.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly guides usage by specifying that the priceId comes from the get_plans tool, indicating a prerequisite. It doesn't explicitly list when not to use, but given the context, it's clear enough.

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