Skip to main content
Glama
Sign In
AgentaOS

AgentaOS

Official
by AgentaOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create product

agenta_products_create

Create a one-time product or subscription plan, set price and billing interval, and get a product ID plus shareable buyer link for checkout or plan changes.

Instructions

Create a product (one-time) or a subscription plan. Creates something buyers can pay for: a one-time product, or a subscription plan with an interval. Returns the product id and its buyer link, which can be shared as is. Use the id with agenta_pay_checkout or as a plan for agenta_subscriptions_change_plan.

Input Schema

NameRequiredDescriptionDefault
nameYesProduct name buyers see
amountYesPrice (e.g. 49.00)
businessNoAct for this business you manage (its id). Omit to act as yourself.
currencyNoCurrency code (e.g. EUR, USD)
intervalNoBilling cadence for a plan: month or year
cancelUrlNohttps URL buyers return to if they back out
trialDaysNoTrial length for a plan, in days
successUrlNohttps URL buyers return to after paying (we append ?sessionId=…)
descriptionNoDescription shown on the checkout page
trialAmountNoPrice of the whole trial (e.g. 9.00). Leave it out and the trial is free
subscriptionNoRecurring plan instead of a one-time product

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.3
    • addedInput schema / properties / business
      Added value: +{
+  "description": "Act for this business you manage (its id). Omit to act as yourself.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / trialAmount
      Added value: +{
+  "description": "Price of the whole trial (e.g. 9.00). Leave it out and the trial is free",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / trialDays / description
      Previous value: -"Free trial length for a plan, in days"New value: +"Trial length for a plan, in days"
  2. Changed3 schema fields changedv0.1.1
    • removedInput schema / properties / business
      Removed value: -{
-  "description": "Act for this business you manage (its id). Omit to act as yourself.",
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / trialAmount
      Removed value: -{
-  "description": "Price of the whole trial (e.g. 9.00). Leave it out and the trial is free",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}
    • changedInput schema / properties / trialDays / description
      Previous value: -"Trial length for a plan, in days"New value: +"Free trial length for a plan, in days"
  3. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / business
      Added value: +{
+  "description": "Act for this business you manage (its id). Omit to act as yourself.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / trialAmount
      Added value: +{
+  "description": "Price of the whole trial (e.g. 9.00). Leave it out and the trial is free",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / trialDays / description
      Previous value: -"Free trial length for a plan, in days"New value: +"Trial length for a plan, in days"
  4. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the call returns the product id and a shareable buyer link, which is genuinely useful since there is no output schema. It still omits auth requirements or rate limits, so a 3 is appropriate.

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

Conciseness4/5

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

Front-loads the verb and resource, and each sentence conveys usable information. There is mild redundancy between the first two sentences ('one-time product or a subscription plan' repeated), which keeps it from a 5.

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?

For an 11-parameter creation tool with no output schema, the description covers both what is created and what is returned, plus how to consume the id. Nothing critical is missing, though deeper behavioral notes would be needed for a 5.

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%, so every parameter is already documented in the schema. The description reinforces the interval/subscription concept but adds no syntax or format detail beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Create a product') and explicitly distinguishes the two output modes it produces: a one-time product versus a subscription plan with an interval. An agent can identify it apart from siblings like agenta_products_list without opening the schema.

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?

Gives downstream routing ('Use the id with agenta_pay_checkout or as a plan for agenta_subscriptions_change_plan'), which clarifies the follow-on context. However, it does not state when to prefer this over alternatives or any prerequisites, so it stops short of explicit when/when-not guidance.

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