Skip to main content
Glama

initiate_license

Start a license purchase for any track, including partner tracks. First ask whether the license is personal (non-commercial) or business. Personal: pass license_type (social_media or all_digital). Business: pass licensee_type "business" with medium, category, territory, and term from get_license_options. Returns a payment_id (like "OCM-Q000123"), the exact USDC amount, the receiving wallet on Base (chain ID 8453), and a terms_url for the license agreement. Before the user pays, confirm the track title and artist in track_to_confirm and the price with them. The user must send the exact amount from the paying_wallet given here; no memo is needed. After the user confirms they sent payment, call verify_license with the payment_id.

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": {
      "track_id": "<track_id>",
      "paying_wallet": "<paying_wallet>"
    },
    "name": "initiate_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoBusiness licenses: term from get_license_options.
emailNoOptional. Email to receive the license and download links.
usageNoOptional. Short description of how the music will be used.
mediumNoBusiness licenses: medium from get_license_options, for example "Social Media Branded Content".
countryNoOptional. Two-letter country code of the licensee, for example "US".
categoryNoBusiness licenses: category from get_license_options.
track_idYesThe track id exactly as returned by search_catalog, ai_search, or get_track, for example "417" or "partner_82". Never remove the "partner_" prefix.
territoryNoBusiness licenses: territory from get_license_options.
license_typeNoPersonal (non-commercial) licenses: social_media (personal videos on TikTok, Instagram, YouTube, X) or all_digital (non-commercial use on websites, podcasts, streaming, and online video). Omit for business licenses.
licensee_nameNoOptional. Person or company that will hold the license. Printed on the agreement.
licensee_typeNoFor rate card licenses (medium, category, territory, term): business (default) or personal.
paying_walletYesThe Base wallet address (0x followed by 40 hex characters) the user will send USDC from.
project_titleNoOptional. Project or production title. Printed on the agreement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"For other uses: category from get_license_options."New value: +"Business licenses: category from get_license_options."
    • changedInput schema / properties / license_type / description
      Previous value: -"social_media (TikTok, Instagram, YouTube, X; non-commercial) or all_digital (advertising, apps, games, podcasts, websites). Omit when using medium, category, territory, and term."New value: +"Personal (non-commercial) licenses: social_media (personal videos on TikTok, Instagram, YouTube, X) or all_digital (non-commercial use on websites, podcasts, streaming, and online video). Omit for business licenses."
    • addedInput schema / properties / licensee_type
      Added value: +{
      +  "description": "For rate card licenses (medium, category, territory, term): business (default) or personal.",
      +  "enum": [
      +    "business",
      +    "personal"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / medium / description
      Previous value: -"For other uses: medium from get_license_options, for example \"Commercials\"."New value: +"Business licenses: medium from get_license_options, for example \"Social Media Branded Content\"."
    • changedInput schema / properties / term / description
      Previous value: -"For other uses: term from get_license_options."New value: +"Business licenses: term from get_license_options."
    • changedInput schema / properties / territory / description
      Previous value: -"For other uses: territory from get_license_options."New value: +"Business licenses: territory from get_license_options."
  2. Changed11 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "For other uses: category from get_license_options.",
      +  "type": "string"
      +}
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Optional. Two-letter country code of the licensee, for example \"US\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "Optional. Email to receive the license and download links.",
      +  "type": "string"
      +}
    • changedInput schema / properties / license_type / description
      Previous value: -"social_media ($5 USDC: TikTok, Instagram, YouTube, X) or all_digital ($35 USDC: advertising, apps, games, podcasts, websites)."New value: +"social_media (TikTok, Instagram, YouTube, X; non-commercial) or all_digital (advertising, apps, games, podcasts, websites). Omit when using medium, category, territory, and term."
    • addedInput schema / properties / licensee_name
      Added value: +{
      +  "description": "Optional. Person or company that will hold the license. Printed on the agreement.",
      +  "type": "string"
      +}
    • addedInput schema / properties / medium
      Added value: +{
      +  "description": "For other uses: medium from get_license_options, for example \"Commercials\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / project_title
      Added value: +{
      +  "description": "Optional. Project or production title. Printed on the agreement.",
      +  "type": "string"
      +}
    • addedInput schema / properties / term
      Added value: +{
      +  "description": "For other uses: term from get_license_options.",
      +  "type": "string"
      +}
    • addedInput schema / properties / territory
      Added value: +{
      +  "description": "For other uses: territory from get_license_options.",
      +  "type": "string"
      +}
    • addedInput schema / properties / usage
      Added value: +{
      +  "description": "Optional. Short description of how the music will be used.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "track_id",
      -  "license_type",
      -  "paying_wallet"
      -]New value: +[
      +  "track_id",
      +  "paying_wallet"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / track_id / description
      Previous value: -"The track ID from search_catalog, ai_search, or get_track."New value: +"The track id exactly as returned by search_catalog, ai_search, or get_track, for example \"417\" or \"partner_82\". Never remove the \"partner_\" prefix."
    • changedInput schema / properties / track_id / type
      Previous value: -"integer"New value: +"string"
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

With annotations covering mutation, open-world, and non-idempotency, the description adds valuable process context: it returns a payment_id, exact USDC amount, receiving wallet on Base (chain 8453), and terms_url. It also warns that the user must send the exact amount with no memo and that confirmation must happen before payment. It does not discuss failure or retry behavior, which keeps it from a 5.

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?

The description is dense but well front-loaded: the primary action and first question come first, followed by branch-specific parameter guidance and then the payment verification flow. Every sentence carries operational information, though it is longer and more prose-heavy than ideal 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 13 parameters, no output schema, and a multi-step payment flow, the description is complete enough to execute correctly. It explains the return values (payment_id, amount, wallet, terms_url), the required user confirmation, and the next tool to call, so no critical context is missing.

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%, so the schema already documents every field. The description goes beyond it by explaining the personal-vs-business branching logic and which parameters belong to each path, including that business fields must come from get_license_options. It also references track_to_confirm and paying_wallet in the confirmation workflow, adding practical meaning beyond field definitions.

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 opens with a specific verb+resource ('Start a license purchase') and scopes it to 'any track, including partner tracks.' It also distinguishes the tool from siblings by naming get_license_options for business parameters and verify_license as the follow-up step.

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

Usage Guidelines5/5

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

It gives explicit branching instructions: first ask personal vs. business; for personal use license_type; for business pass licensee_type plus rate-card fields from get_license_options. It also states the exact next action after payment (call verify_license), leaving no ambiguity about alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources