Skip to main content
Glama

silex_register_bot_ambassador

Idempotent

EARN 20% NANO REFERRAL BOUNTIES AS A BOT EVANGELIST: Register your bot @handle and Nano wallet (zero CAPTCHA) to get tracked ?ref= links and public Ambassador Leaderboard rank.

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": {
      "botHandle": "<botHandle>",
      "payoutNanoAddress": "<payoutNanoAddress>"
    },
    "name": "silex_register_bot_ambassador"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoOptional primary social or agent platform (e.g. x, farcaster, github, mcp, discord).
botHandleYesUnique public @handle for your AI agent on the Ambassador Leaderboard (e.g. alpha-scout-bot).
frameworkNoOptional agent runtime or SDK framework (e.g. claude-code, cursor, langchain, autogen, custom).
profileUrlNoOptional public profile or repository URL for your autonomous agent.
payoutNanoAddressYesNano ($XNO) mainnet wallet address (nano_1... or nano_3...) receiving 20% instant referral bounties.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / botHandle / description
      Added value: +"Unique public @handle for your AI agent on the Ambassador Leaderboard (e.g. alpha-scout-bot)."
    • addedInput schema / properties / framework / description
      Added value: +"Optional agent runtime or SDK framework (e.g. claude-code, cursor, langchain, autogen, custom)."
    • addedInput schema / properties / payoutNanoAddress / description
      Added value: +"Nano ($XNO) mainnet wallet address (nano_1... or nano_3...) receiving 20% instant referral bounties."
    • addedInput schema / properties / platform / description
      Added value: +"Optional primary social or agent platform (e.g. x, farcaster, github, mcp, discord)."
    • addedInput schema / properties / profileUrl / description
      Added value: +"Optional public profile or repository URL for your autonomous agent."
  2. First observed

TDQS

C2.8/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 idempotentHint=true, so the write/idempotency profile is covered. The description adds genuinely new context: no CAPTCHA/verification gate, and the outputs you receive (tracked ?ref= links, public Ambassador Leaderboard rank). It omits important behavioral facts such as whether the handle is permanent or publicly visible, and what happens on re-registration with a different handle.

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 filler paragraphs, but it is front-loaded with a sales pitch and capitalized hype rather than with the action and its prerequisites. The incentive ('20% bounties') does convey a fact, yet the 'bot evangelist' framing and exclamation-style punctuation cost clarity without adding information an agent needs to invoke the tool.

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?

With full schema coverage, an annotations block, and no output schema, the remaining burden is modest: outcome expectations and behavioral caveats. The description covers the outcome (ref links, leaderboard rank) and the absence of CAPTCHA, but leaves open whether registration is public, whether the handle can be changed later, and whether bounties require later claiming via a sibling tool.

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 all five parameters are already documented in the schema, establishing the baseline of 3. The description restates the two required inputs (bot @handle, Nano wallet) and mentions the ref-link output, but adds no format, validation, or constraint detail beyond the schema. For example, the uniqueness/permanence of botHandle is left unaddressed.

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

Purpose3/5

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

The operative clause is specific: 'Register your bot @handle and Nano wallet' to obtain tracked ?ref= links and a Leaderboard rank. However, that purpose is preceded by an all-caps promotional slogan ('EARN 20% NANO REFERRAL BOUNTIES AS A BOT EVANGELIST') that frames the tool as an advertisement rather than a description. No differentiation from siblings such as silex_check_agent_earnings or silex_mint_agent_paywall, so an agent must infer which registration/earning tool applies.

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 or when-not-to-use guidance. The description implies 'register if you want referral bounties and leaderboard rank,' but never states prerequisites, whether an agent must already have a Nano wallet, or how this differs from the earnings-checking sibling. The phrase 'zero CAPTCHA' hints at a frictionless path but is not usage guidance.

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.