Loading ToolBench
MCP server providing tools for queries and transactions to the Ambur Marketplace contract on Archway Network. Allows users to list contract deployments, query entry points, build query messages, list execute entry points, and build execute messages for the Ambur NFT marketplace.
Ambur MCP has clear, domain-specific tool names (list_*, build_*) and detailed descriptions that explain WHAT each tool does and WHEN to use it. However, critical gaps undermine production readiness: (1) Most tools accept empty input schemas ({}), providing no parameter validation or LLM guidance on required fields. (2) Parameters like 'query_msg' and 'execute_msg' are documented as 'JSON stringified' but lack format constraints, length limits, or validation rules, LLMs will hallucinate invalid JSON. (3) No output schemas are documented; LLMs cannot predict response structure or plan downstream calls. (4) Error handling is absent, no guidance on retryability, user-fixable errors, or recovery paths. (5) build_execute_msg accepts 'funds' array but lacks per-item validation or examples. Descriptions are strong (100-250 chars, well-structured), but parameter-level rigor is missing.
Call this tool to build a prepared execute message (transaction message) for the Ambur NFT marketplace contract. This tool won't sign or broadcast the transaction, but can be combined with any wallet-enabled tool that can sign and broadcast Cosmos transactions.
Call this tool to build a prepared query message for a query to the Ambur NFT marketplace contract. This tool won't broadcast the query or return the query result, but can be combined with any RPC connected query tool that accepts a well-formed Cosmos QueryRequest.
Call this tool to get a list of contract addresses, and associated Archway Network, where the Ambur marketplace contract has been deployed. This tool is helpful for discovering the mainnet and testnet contract addresses for the Ambur marketplace smart contract.
Call this tool to get a list of NFT collections that can be traded in the Ambur marketplace contract. The detailed response will provide the following information about each NFT collection: ```DOCUMENTATION_BEGIN * Collection name * Collection description * Collection contract addresses for the token contract (the nft) and the minter contract (a manager contract that operates as admin over the token contract) - Users will need to make txs to the minter contract for certain behaviours, including: minting NFTs, revealing NFT metadata, and redeeming Foresight NFTs for entry into the whitelist for minting newly launching collections. ```DOCUMENTATION_END This tool is helpful for discovering the mainnet and tesnet contract addresses for tokens listed for trading in the Ambur marketplace smart contract.
Five of seven tools have empty input schemas ({}). No parameter validation, type hints, or LLM guidance. LLMs cannot infer what fields are required or their formats.
Parameters 'query_msg' and 'execute_msg' documented as 'JSON stringified' but lack format constraints, length limits, or validation rules. LLMs will hallucinate invalid JSON structures.
No output schemas documented for any tool. LLMs cannot predict response structure, field names, or types. Breaks tool chaining and forces LLMs to guess at downstream field names.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Call this tool to get a list of possible queries that can be made (e.g. query entry points) to the Ambur marketplace contract, as well as their associated calling parameters. This tool is helpful for discovering what parameters a user must provide in order to build a prepared query message for a query to the Ambur NFT marketplace smart contract. The response provided from this tool is a JSON schema for the QueryMsg enum of the Ambur maketplace contract. It would be too verbose to provide it to your chat partner, so summarizing it will be crucial.
Call this tool to get a JSON schema for common query response types. This tool is useful when your chat partner asks for more information about a specific query, if you've already called the 'list_query_entry_points' tool and it has informed you of the return type for the query. The output from this tool is an object containing the JSON schema for the following custom (developer) defined types: ```DOCUMENTATION_BEGIN ### All Query Return Types: * `CollectionOfferDetailsResponse` * `CollectionRoyaltiesResponse` * `DetailsResponse` * `ListResponse` **Notes:** * `CollectionRoyaltiesResponse` has a sub-field called `fee_percentage` that has a format of `uint64` in Rust and a type of `integer` in JSON representation. This 'fee_percentage' is a whole number with a minimum value of 0 (e.g. 0% fees) and a maximum value of 30 (e.g. 30% fees). `fee_percentage` is _not_ currently denominated in basis points. ```DOCUMENTATION_END
Call this tool to get a list of possible execute (transaction) entry points that can be called on the Ambur marketplace contract, as well as their associated calling parameters.
No error handling guidance. Tools do not document what errors are retryable, user-fixable, or fatal. No recovery paths or actionable error messages defined.
build_execute_msg 'funds' parameter is an array of Coin objects but lacks per-item validation, min/max array length, or examples. LLMs may pass malformed or empty arrays.