Skip to main content
Glama
thenavidm

Lemon Squeezy MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create usage record

create_usage_record
Destructive

Create usage records to track metered subscription usage. Choose increment or set actions and specify quantity for accurate billing.

Instructions

Create a usage record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
accountNoExact private profile label. Does not prove store ownership; mode applies to the main API key only.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete native JSON object body. JSON:API uses data/type/id/attributes/relationships. No mixing with body flags or payload_file. License credential is private configuration, never body input.
quantityNo
payload_fileNoAbsolute regular non-symlink native JSON body file at most 1 MiB; cannot mix with payload or body flags.
subscription_item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Explicit approval for this requested effect, including private output files."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv2.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already state destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds no further behavioral context such as mutation impact, confirmation expectations, or authorization requirements. It does not contradict the annotations, but it provides no value beyond them.

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 single sentence is front-loaded and technically concise, but it is under-specified rather than appropriately concise. It repeats the name/title without earning its place by adding any actionable detail.

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

Completeness1/5

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

For a complex mutation with nested JSON:API payload structure, 7 parameters, no output schema, and no required fields, the description is completely inadequate. It leaves the agent without guidance on required body shape, alternates like payload_file, confirmation semantics, or destructive effects.

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?

The description adds no meaning for any of the 7 parameters, including the action enum, quantity, payload/payload_file alternatives, account, confirm, or subscription_item_id. Schema description coverage is only 57%, so the description should compensate, but it does not.

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 'Create a usage record' merely restates the tool name and title with no additional specificity. It does not distinguish this creation tool from related siblings like list_usage_records, get_usage_record, or get_subscription_item_current_usage.

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 guidance on when to use this tool instead of alternatives, what prerequisites are needed, or when a read/update sibling would be more appropriate. The description only names the operation.

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