Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

3land_createCollection

Create a new NFT collection on the 3.Land marketplace by defining its owner, name, symbol, and cover image.

Instructions

Create a new NFT collection on 3.Land marketplace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCollection name
imageYesCollection cover image URL
ownerYesCollection owner wallet
symbolYesCollection symbol
creatorsNo
royaltyBpsNo
descriptionNoCollection description
Behavior2/5

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

No annotations are provided, so the description bears full burden. It does not disclose any behavioral traits such as requiring wallet signature, on-chain effects, or Authorization needs. Minimal transparency.

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?

The description is a single sentence, concise and front-loaded. However, it is slightly under-specified for a tool with 7 parameters, making it borderline.

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?

Given the complexity (7 params, no output schema, no annotations), the description is very incomplete. It omits details about the collection creation process, expected outcomes, and potential side effects.

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 71%, but the description adds no additional meaning about parameters beyond what is in the schema. It does not help an agent understand parameter relationships or constraints.

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 clearly states the action 'Create a new NFT collection' and specific platform '3.Land marketplace'. It is a specific verb+resource, but does not differentiate from similar sibling tools like metaplex-nft_deployCollection.

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?

No guidance on when to use this tool versus alternatives (e.g., other collection creation tools). The description does not mention context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OOBE-PROTOCOL/sap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server