Skip to main content
Glama

AgentPad

by com.thevibehosting.agentpad
OverviewDiscussionsAdmin

build_launch_tx

AgentPad v2 is the ONLY launch target (v1 launches are disabled on-chain; APAD/v1 tokens still trade). Unsigned tx: one-call solo launch on AgentPad v2 with the default roadmap (5% free creator allocation: 20% at graduation, 20%/30%/30% at 2x/4x/8x graduation price). Launch fee 0; initialBuyEth optional. Creator earns 0.50% of every curve trade. REQUIRED (2.4.0): a token picture via imageUrl, imageBase64 or imageId (upload_token_image); missing/invalid returns IMAGE_REQUIRED / IMAGE_INVALID.

Input Schema

NameRequiredDescriptionDefault
nameYes
symbolYes
imageIdNoid returned by upload_token_image
imageUrlNoREQUIRED unless imageId/imageBase64 is given: https:// (or ipfs://) link to a PNG, JPEG, WebP or GIF, min 64x64, max 2 MB. We fetch, validate and re-host it.
descriptionNo
imageBase64Noraw base64 or data:image/...;base64,... of the picture (max 2 MB)
metadataURINooptional: your own https:// or ipfs:// JSON; by default we host metadata with your picture
initialBuyEthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "maxLength": 280,
+  "type": "string"
+}
    • addedInput schema / properties / imageBase64
      Added value: +{
+  "description": "raw base64 or data:image/...;base64,... of the picture (max 2 MB)",
+  "type": "string"
+}
    • addedInput schema / properties / imageId
      Added value: +{
+  "description": "id returned by upload_token_image",
+  "type": "string"
+}
    • addedInput schema / properties / imageUrl
      Added value: +{
+  "description": "REQUIRED unless imageId/imageBase64 is given: https:// (or ipfs://) link to a PNG, JPEG, WebP or GIF, min 64x64, max 2 MB. We fetch, validate and re-host it.",
+  "type": "string"
+}
    • changedInput schema / properties / metadataURI / description
      Previous value: -"https:// or ipfs:// JSON with name, description, image"New value: +"optional: your own https:// or ipfs:// JSON; by default we host metadata with your picture"
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "symbol",
-  "metadataURI"
-]New value: +[
+  "name",
+  "symbol"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: unsigned (not submitted), launch fee 0, creator royalty 0.50% of curve trade volume, the default 5% roadmap vesting schedule, and the IMAGE_REQUIRED/IMAGE_INVALID failure codes. It omits who signs/broadcasts the returned tx and whether name/symbol must be unique on-chain.

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?

Front-loaded with the version constraint, then economics, then the hard requirement; every clause carries information. It is dense – heavy parentheticals and an embedded vesting schedule – but not padded.

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?

For an 8-parameter mutation/tx-building tool with no annotations and no output schema, the description covers versioning, economics, image requirement and default roadmap. Gaps remain on initialBuyEth behavior, name/symbol validation, and what the returned unsigned tx payload contains.

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% and the description compensates for the image parameters (imageUrl/imageBase64/imageId with upload_token_image) and metadata hosting defaults. It adds nothing about initialBuyEth beyond 'optional' – no units, format, or curve effect – and says nothing about name/symbol constraints despite symbol being capped at 16 chars.

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?

States a specific verb+resource (build an unsigned one-call solo launch tx on AgentPad v2) and pins the launch target version. The word 'solo' implicitly separates it from build_team_launch_tx in the sibling list, so an agent can route between the two launch builders.

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?

Explicitly says v2 is the ONLY launch target and that v1 launches are disabled on-chain (v1 tokens still trade), which prevents a wrong-version call. It routes to upload_token_image for the required picture but never states when to prefer build_team_launch_tx over this solo path.

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

All AgentPad toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources