Skip to main content
Glama

Create Zero Link

create_zero_link

Create a Zero Link product for a community managed by the authenticated Nas.com user. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "currency": "<currency>",
      "pricingConfig": "<pricingConfig>"
    },
    "name": "create_zero_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoTitle shown to members.
amountNoPrice amount in the business currency.
statusNoStatus value; use one of the allowed values in this schema.
messageNoMessage text to send to AI Cofounder.
coverImgNo
currencyYesThree-letter ISO 4217 currency code, for example USD.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
redirectLinkNo
pricingConfigYesPricing configuration for the item.
passOnTakeRateNoWhether to pass the processing fee on to buyers.
passOnPaymentGatewayFeeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / amount / description
      Added value: +"Price amount in the business currency."
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / currency / description
      Added value: +"Three-letter ISO 4217 currency code, for example USD."
    • addedInput schema / properties / message / description
      Added value: +"Message text to send to AI Cofounder."
    • addedInput schema / properties / passOnTakeRate / description
      Added value: +"Whether to pass the processing fee on to buyers."
    • addedInput schema / properties / pricingConfig / description
      Added value: +"Pricing configuration for the item."
    • addedInput schema / properties / status / description
      Added value: +"Status value; use one of the allowed values in this schema."
    • addedInput schema / properties / title / description
      Added value: +"Title shown to members."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false. The description adds real behavioral context beyond that: a permission gate, a permanent tier-based exclusion, grace-period messaging, and a blocking condition. It does not disclose what creation actually does — default status, whether the link is live on creation, or what the call returns — which is why it stops short of 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?

Purpose comes first, then the gating rules, which is the right order for a mutation tool with a hard precondition. There is mild redundancy between 'check business permissions' and 'Call check_business_tool_access,' but every sentence carries actionable content.

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

Completeness3/5

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

For an 11-parameter mutation with a nested pricing object and no output schema, the definition covers the access-gating dimension thoroughly but leaves the functional dimension thin. An agent still cannot tell what a successful create returns or what state the Zero Link lands in, though the absence of an output schema makes some of that excusable.

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?

With 73% schema description coverage, the schema already documents communityId, currency, amount, title, status, and pricingConfig, so the baseline is 3. The description contributes no parameter-level meaning at all — it never mentions pricingConfig.priceType, the FIXED/FLEXIBLE choice, or the two pass-on-fee flags, some of which remain undocumented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Create a Zero Link product for a community managed by the authenticated Nas.com user.' That distinguishes it cleanly from publish_zero_link, update_zero_link, and delete_zero_link. It does not explain what a 'Zero Link product' actually is, so an agent unfamiliar with the domain gets no definition of the artifact being created.

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 names a concrete precondition and the sibling that checks it: 'Call check_business_tool_access before collecting inputs.' It also states an explicit exclusion ('FREE businesses cannot use this tool, regardless of individual feature rows') and a hard stop ('never proceed when access is blocked'), plus an instruction to surface grace-period warnings and resubscribe links. This is exactly the when/when-not/alternative routing that prevents misuse.

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