Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

3land_listForSale

List an NFT for sale on 3.Land using any SPL token. Provide seller public key, NFT mint, and price to create the listing.

Instructions

List an NFT for sale on 3.Land in any SPL token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYesNFT mint to list
priceYesListing price (in specified token)
expiryNoISO 8601 listing expiry timestamp
sellerYesSolana public key (base58)
priceMintNoNFT mint address (base58)
Behavior2/5

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

With no annotations, the description bears full burden for behavioral disclosure, but it only states the action ('list an NFT for sale') without explaining side effects (e.g., on-chain transaction, approval requirements, fees, or success/failure conditions). The minimal depth leaves the agent uninformed.

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 a single, front-loaded sentence with no unnecessary words. It efficiently conveys the core purpose, earning a high score for conciseness.

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 tool has 5 parameters, no output schema, and no annotations, the description is too brief. It omits crucial context such as what happens after listing (transaction outcomes), prerequisites (e.g., ownership, approvals), or error states, leaving the agent with incomplete information for safe invocation.

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 100%, so baseline is 3. The description adds value by clarifying that 'priceMint' refers to any SPL token (schema description incorrectly says 'NFT mint address'), but does not elaborate further on other parameters like 'expiry' or 'seller' beyond schema descriptions.

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 clearly states the tool lists an NFT for sale on 3.Land in any SPL token. It uses a specific verb ('List') and resource ('NFT'), and the platform name distinguishes it from sibling tools like '3land_buyNFT' and '3land_cancelListing'.

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?

The description does not provide any guidance on when to use this tool versus alternatives (e.g., '3land_mintAndList' for simultaneous minting and listing, or '3land_cancelListing' to remove a listing). No prerequisites or exclusions are mentioned.

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