Skip to main content
Glama
Sign In
@yawlabs/lemonsqueezy-mcp

@yawlabs/lemonsqueezy-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ls_update_subscription_item

DestructiveIdempotent

Modify a subscription item's quantity for seat-based or quantity-based billing. Provide the item ID and new quantity to adjust usage.

Instructions

Update a subscription item's quantity. Used for seat-based or quantity-based billing.

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": {
      "subscriptionItemId": "<subscriptionItemId>",
      "quantity": "<quantity>"
    },
    "name": "ls_update_subscription_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYesNew quantity for the subscription item
subscriptionItemIdYesThe subscription item ID to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.10

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint:true, idempotentHint:true, and openWorldHint:true, which cover the main behavioral traits. The description adds no additional behavioral context beyond what the annotations provide, so it meets the baseline but does not exceed it.

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 two sentences that are front-loaded and efficient. Every word adds value, with no redundancy or 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?

Given the low complexity, schema coverage, and annotations, the description is nearly complete. However, it does not mention the return value or response format, which would be helpful for an update tool. Still, it is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with both parameters having clear descriptions. The description repeats the schema action without adding new meaning, so it scores the baseline for high coverage.

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 verb 'Update', the resource 'subscription item', and the specific attribute 'quantity'. It distinguishes from siblings by noting 'Used for seat-based or quantity-based billing', which differentiates it from other update tools like ls_update_customer.

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 provides context for when to use the tool ('seat-based or quantity-based billing'), but does not explicitly state when not to use it or mention alternatives. This is sufficient but could be improved with exclusions.

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