@thryx/mcp-server

thryx_launch

Launch a new ERC-20 token on Base without paying gas fees. Provide name, symbol, and image; the tool returns token address and transaction hash.

Instructions

Launch a new token on Base (gasless). The platform pays gas via paymaster. Returns tokenAddress + txHash. Requires THRYX_API_KEY. Image required (public URL or data: URL).

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": {
      "name": "<name>",
      "symbol": "<symbol>",
      "image": "<image>"
    },
    "name": "thryx_launch"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Display name, e.g. "My Agent Coin".
`image`	Yes	Image URL (https:// public URL) or data: URL. PNG/JPEG/GIF/WebP, under 400KB.
`symbol`	Yes	Ticker, 1–12 chars, will be uppercased.
`article`	No	Optional long-form article body, max ~10K chars.
`twitter`	No
`website`	No
`telegram`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Aug 4, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that gas is paid via paymaster, the tool returns tokenAddress + txHash, and an API key is required. However, it does not mention that launching a token is an irreversible on-chain write, nor any failure modes or rate limits, which are relevant for a state-changing tool.

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

Conciseness5/5

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

The description is concise and front-loaded with the core action. Every sentence adds a distinct piece of information: gasless mechanism, return values, auth requirement, and image constraint. No redundant filler.

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?

Given the moderate complexity (8 params, no output schema, no annotations), the description covers essential invocation facts: purpose, chain, gas handling, return values, auth, and a key parameter constraint. Optional social fields are self-explanatory and the schema provides URI formats. It stops short of failure/error details but is otherwise sufficient for an agent to invoke correctly.

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 50%, so the description must compensate partially. It adds the important external parameter THRYX_API_KEY and restates the image requirement, but it does not clarify the purpose of the optional social/link parameters (twitter, website, telegram) or the 'description' field beyond what the schema provides.

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 states a specific action: 'Launch a new token on Base (gasless)', identifying both the verb and resource. It also distinguishes this tool from siblings (e.g., thryx_buy, thryx_claim) by focusing on token creation and explicitly mentioning the return values tokenAddress + txHash.

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?

The description provides clear context: use this to launch a new token on Base with gasless execution. It does not explicitly name alternatives or when-not-to-use scenarios, but the unique action and the prerequisite (THRYX_API_KEY) give adequate usage direction.

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