Skip to main content
Glama

NFTm

by app.nftm
OverviewDiscussionsAdmin

Server Details

Quote an NFTm launch. The creator signs in Phantom.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: nftm_quote_launch only estimates SOL cost, while nftm_launch_collection creates the launch page and initiates transactions. Their descriptions further separate wallet requirements and confirmation behavior, leaving no realistic confusion.

Naming Consistency5/5

Both tools use a consistent nftm_<verb>_<noun> snake_case pattern: nftm_launch_collection and nftm_quote_launch. The shared prefix and predictable verb-object structure make the naming coherent.

Tool Count3/5

Two tools is thin for an NFT launch service, even if the server intentionally focuses only on quoting and launch initiation. The surface is borderline rather than clearly well-scoped, since broader lifecycle operations would normally be expected.

Completeness3/5

The server covers quoting and launch initiation, but it lacks status, retrieval, update, cancel, or post-launch verification tools. These are notable gaps for an NFT collection launch workflow, though some steps may be handled externally.

Available Tools

2 tools
nftm_launch_collectionLaunch an NFTm collectionA
Destructive
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
imagesNo
supplyNo
confirmNo
traitsCsvNo
mintPriceSolNo
collectionNameNo
royaltyPercentNo
confirmHighValueNo

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.

nftm_quote_launchQuote an NFTm launchA
Read-only
Inspect

Quotes the SOL cost of an NFTm launch from pictures and an optional traits spreadsheet. Uses the same published figures as the NFTm launch cost calculator. This tool does not upload files and does not need a wallet.

ParametersJSON Schema
NameRequiredDescriptionDefault
imagesNo
supplyNo
traitsCsvNo
mintPriceSolNo
collectionNameNo

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it does not upload files and does not need a wallet, which helps an agent understand side effects and authentication expectations.

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 short sentences with zero waste, front-loading what the tool does. The additional notes about published figures and lack of wallet/file upload are relevant and proportionate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, 0% schema description coverage, and no output schema, the description leaves too much unspecified. It covers the high-level purpose and safety context but does not explain what the quote output contains or what most input parameters mean, making correct invocation harder.

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

Parameters2/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 compensate, but it only vaguely mentions pictures and an optional traits spreadsheet. It does not explain supply, mintPriceSol, collectionName, or how the images array fields are used, leaving most parameter meaning undocumented.

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 and resource: quotes the SOL cost of an NFTm launch from pictures and an optional traits spreadsheet. It clearly distinguishes itself from the sibling nftm_launch_collection, which performs the actual launch rather than estimating cost.

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 description implies usage for cost estimation before launching, but does not explicitly say when to use this tool versus nftm_launch_collection. It provides useful context that it does not upload files and does not need a wallet, but no explicit alternatives or exclusions are given.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changednftm_launch_collection3 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"
+]
    • Changednftm_quote_launch3 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. 2 tool updates
    • First observednftm_launch_collection
    • First observednftm_quote_launch

Related MCP Connectors

Related MCP Servers

  • labs

    koynlabs
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables launching tokens on pump.fun and StonkFun with user-signed transactions, plus a disclosed two-sided quoter for market making.
    MIT

  • jupiter-quotes

    Br0ski777
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables fetching best swap quotes on Solana via Jupiter aggregator with pay-per-call x402 micropayments.
    MIT
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