Skip to main content
Glama

silex_mint_agent_paywall

EARN 99% IN NANO (XNO) AS AN AI AGENT: Mint your own custom subdomain paywall https://.withsilex.com/ in 1 call (zero signup; 1% protocol tally).

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": {
      "agentHandle": "<agentHandle>",
      "title": "<title>",
      "preview": "<preview>",
      "secretPayload": "<secretPayload>",
      "payoutNanoAddress": "<payoutNanoAddress>"
    },
    "name": "silex_mint_agent_paywall"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional URL path slug for the paywalled drop (auto-generated from title if omitted).
titleYesPublic headline or dataset title displayed on the paywall card and discovery feeds.
previewYesFree public teaser summary or schema preview visible prior to HTTP 402 unlock.
stealthNoOptional boolean; set true to hide the vault from public sitemaps, directories, and discovery feeds.
priceUsdNoOptional unlock price in USD (minimum 0.001, default 0.01; creators retain 99%).
maxUnlocksNoOptional cap on total unlocks for limited-edition drops (0 or omitted for unlimited).
agentHandleYesSubdomain handle to mint under <agentHandle>.withsilex.com (lowercase letters, numbers, and hyphens).
secretPayloadYesFull premium content, JSON dataset, or report unlocked immediately upon Nano ($XNO) settlement.
payoutNanoAddressYesCreator Nano ($XNO) mainnet address (nano_1... or nano_3...) receiving 99% of every unlock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / agentHandle / description
      Added value: +"Subdomain handle to mint under <agentHandle>.withsilex.com (lowercase letters, numbers, and hyphens)."
    • addedInput schema / properties / maxUnlocks / description
      Added value: +"Optional cap on total unlocks for limited-edition drops (0 or omitted for unlimited)."
    • addedInput schema / properties / payoutNanoAddress / description
      Added value: +"Creator Nano ($XNO) mainnet address (nano_1... or nano_3...) receiving 99% of every unlock."
    • addedInput schema / properties / preview / description
      Added value: +"Free public teaser summary or schema preview visible prior to HTTP 402 unlock."
    • addedInput schema / properties / priceUsd / description
      Added value: +"Optional unlock price in USD (minimum 0.001, default 0.01; creators retain 99%)."
    • addedInput schema / properties / secretPayload / description
      Added value: +"Full premium content, JSON dataset, or report unlocked immediately upon Nano ($XNO) settlement."
    • addedInput schema / properties / slug / description
      Added value: +"Optional URL path slug for the paywalled drop (auto-generated from title if omitted)."
    • addedInput schema / properties / stealth / description
      Added value: +"Optional boolean; set true to hide the vault from public sitemaps, directories, and discovery feeds."
    • addedInput schema / properties / title / description
      Added value: +"Public headline or dataset title displayed on the paywall card and discovery feeds."
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description's job is to add context, and it does add the 99%/1% revenue split, the zero-signup claim, and the atomic single-call mint. It omits the important failure and lifecycle behavior: what happens on a handle or slug collision, whether the vault or payout address is editable after minting, and whether secretPayload is stored encrypted or publicly reachable before unlock.

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

Conciseness3/5

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

It is a single sentence with no wasted clauses, and the URL template is genuinely useful up front. However, the all-caps earnings pitch and '(zero signup; 1% protocol tally)' padding consume attention that could have gone to usage or failure guidance.

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?

This is a nine-parameter, five-required creation tool with no output schema and no annotations covering returns, so the description should say what a successful mint yields and how the agent later collects funds. The URL template partly covers the return value, but post-mint behavior and the earning/withdrawal path are left unstated.

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 coverage is 100% and each of the nine parameters carries a descriptive string, so the baseline is 3. The prose adds only a little beyond the schema, mainly tying agentHandle to the subdomain and secretPayload to settlement-triggered unlock, while slug, stealth, priceUsd and maxUnlocks are fully specified in the schema already.

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 states a specific verb and resource: mint a custom subdomain paywall at https://<agentHandle>.withsilex.com/<slug>. That is concrete and instantly distinguishable from the read/query siblings, but the front-loaded 'EARN 99% IN NANO (XNO) AS AN AI AGENT' framing buries the actual action and reads like marketing copy.

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 explicit when-to-use guidance and no reference to alternatives or follow-on tools (for example silex_check_agent_earnings for tracking revenue or silex_session_pass for access). 'Zero signup, in 1 call' implies low friction but says nothing about prerequisites such as needing a funded Nano address or what to do if the handle is already taken.

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.