Skip to main content
Glama

NFTm

by app.nftm
OverviewDiscussionsAdmin

Launch an NFTm collection

nftm_launch_collection
Destructive

Saves a one-time NFTm page where the creator approves two transactions in Phantom: the collection, then the mint setup. Requires confirm: true. A quote over 10 SOL also requires confirmHighValue: true. This tool does not upload, sign, or create a store, and it does not accept a private key or an art folder id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNo
supplyNo
confirmNo
traitsCsvNo
mintPriceSolNo
collectionNameNo
royaltyPercentNo
confirmHighValueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / images / items / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / images / items / properties
      Added value: +{
+  "bytesBase64": {
+    "description": "Raw image bytes as base64. Optional when sizeBytes alone is enough for a quote.",
+    "type": "string"
+  },
+  "filename": {
+    "description": "Image filename ending in .png, .jpg, .jpeg, .gif, or .webp",
+    "type": "string"
+  },
+  "sizeBytes": {
+    "description": "Size in bytes. Required when bytesBase64 is omitted.",
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  "url": {
+    "description": "https URL of the image. Optional.",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / images / items / required
      Added value: +[
+  "filename"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false. The description adds notable value by disclosing that the creator approves two transactions and that quote>10 SOL requires confirmHighValue=true — real behavioral context. However, it doesn't state what the launch destroys or whether it's reversible, which is the key gap given destructiveHint=true.

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?

Three tight sentences, front-loaded with the core action, then the confirmation rules, then the exclusions. No filler.

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 8-parameter destructive write tool with no output schema and 0% schema coverage, the description covers the confirmation gates but leaves the majority of parameters (images, supply, mintPriceSol, royaltyPercent, traitsCsv, collectionName) undocumented. It's adequate for the confirmation flow but incomplete for full parameter understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It clarifies the confirm and confirmHighValue booleans (the threshold of 10 SOL is especially useful), but the other six parameters (images, supply, traitsCsv, mintPriceSol, collectionName, royaltyPercent) get no description-level explanation. Better than baseline given the confirm semantics, but incomplete.

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 action — saving an NFTm page where the creator approves two Phantom transactions — which clearly goes beyond the title. It doesn't explicitly name the sibling nftm_quote_launch, so it misses full differentiation, but the 'does not upload, sign, or create a store' exclusions help bound the tool's scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The confirm/confirmHighValue conditions imply usage context, but there is no explicit when-to-use vs nftm_quote_launch guidance (e.g., 'quote first, then launch'). An agent must infer the sequence from the sibling name.

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

All NFTm 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