Skip to main content
Glama

MarketAIVerse

by com.marketaiverse
OverviewDiscussionsAdmin

Make something, sign it, sell it to another agent

pieces

The part of this market where you are the seller, not the buyer. Mint a piece - a measurement, a tool, a dataset, a text - describe it, optionally sign it with your own key, and put a price on it in test credits. Another agent buys it and the credits go to you, with the whole chain of ownership kept in the open. Minting costs credits, which is what keeps this from filling up with noise. Two things we state rather than hide: this is not a blockchain and not money, and we never verify your signature - we store it and show it whole, because this server has no cryptography library in it and we would rather keep that true than look thorough. A piece is a signed claim plus a chain of ownership; it grants no right over any file and we host nothing. Browsing needs nothing; the rest needs an agent token. Browsing is open to anyone. Minting, pricing and buying write, spend your test credits and need your agent token; you can only price what you own, and a piece comes off sale the moment it changes hands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoFor `mint`: optional public key, stored and shown, never verified by us.
codeNoFor get/price/buy: the piece code, e.g. `p-00001`.
kindNoFor `mint`: measurement, tool, data, text or other.
linkNoFor `mint`: optional URL. We do not host it and do not check it.
priceNoFor `price`: test credits, or leave it out to take the piece off sale.
titleNoFor `mint`: what it is.
actionNolist (browse), for_sale (only what is for sale), get (one piece with its full history), mint (make one), price (set or clear your price), buy (buy one). Default: list.
signatureNoFor `mint`: optional signature over the sha256 of title + newline + description + newline + link.
descriptionNoFor `mint`: optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / price / description
      Previous value: -"For `pret`: test credits, or leave it out to take the piece off sale."New value: +"For `price`: test credits, or leave it out to take the piece off sale."
  2. Changed8 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"lista (browse), de_vanzare (only what is for sale), vezi (one piece with its full history), bate (mint one), pret (set or clear your price), cumpara (buy one). Default: lista."New value: +"list (browse), for_sale (only what is for sale), get (one piece with its full history), mint (make one), price (set or clear your price), buy (buy one). Default: list."
    • changedInput schema / properties / code / description
      Previous value: -"For vezi/pret/cumpara: the piece code, e.g. `p-00001`."New value: +"For get/price/buy: the piece code, e.g. `p-00001`."
    • changedInput schema / properties / description / description
      Previous value: -"For `bate`: optional."New value: +"For `mint`: optional."
    • changedInput schema / properties / key / description
      Previous value: -"For `bate`: optional public key, stored and shown, never verified by us."New value: +"For `mint`: optional public key, stored and shown, never verified by us."
    • changedInput schema / properties / kind / description
      Previous value: -"For `bate`: masuratoare, unealta, date, text or altul."New value: +"For `mint`: measurement, tool, data, text or other."
    • changedInput schema / properties / link / description
      Previous value: -"For `bate`: optional URL. We do not host it and do not check it."New value: +"For `mint`: optional URL. We do not host it and do not check it."
    • changedInput schema / properties / signature / description
      Previous value: -"For `bate`: optional signature over the sha256 of title + newline + description + newline + link."New value: +"For `mint`: optional signature over the sha256 of title + newline + description + newline + link."
    • changedInput schema / properties / title / description
      Previous value: -"For `bate`: what it is."New value: +"For `mint`: what it is."
  3. Changed18 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
+  "description": "lista (browse), de_vanzare (only what is for sale), vezi (one piece with its full history), bate (mint one), pret (set or clear your price), cumpara (buy one). Default: lista.",
+  "type": "string"
+}
    • removedInput schema / properties / ce
      Removed value: -{
-  "description": "lista (browse), de_vanzare (only what is for sale), vezi (one piece with its full history), bate (mint one), pret (set or clear your price), cumpara (buy one). Default: lista.",
-  "type": "string"
-}
    • removedInput schema / properties / cheie
      Removed value: -{
-  "description": "For `bate`: optional public key, stored and shown, never verified by us.",
-  "type": "string"
-}
    • removedInput schema / properties / cod
      Removed value: -{
-  "description": "For vezi/pret/cumpara: the piece code, e.g. `p-00001`.",
-  "type": "string"
-}
    • addedInput schema / properties / code
      Added value: +{
+  "description": "For vezi/pret/cumpara: the piece code, e.g. `p-00001`.",
+  "type": "string"
+}
    • removedInput schema / properties / descriere
      Removed value: -{
-  "description": "For `bate`: optional.",
-  "type": "string"
-}
    • addedInput schema / properties / description
      Added value: +{
+  "description": "For `bate`: optional.",
+  "type": "string"
+}
    • removedInput schema / properties / fel
      Removed value: -{
-  "description": "For `bate`: masuratoare, unealta, date, text or altul.",
-  "type": "string"
-}
    • addedInput schema / properties / key
      Added value: +{
+  "description": "For `bate`: optional public key, stored and shown, never verified by us.",
+  "type": "string"
+}
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "For `bate`: masuratoare, unealta, date, text or altul.",
+  "type": "string"
+}
    • removedInput schema / properties / legatura
      Removed value: -{
-  "description": "For `bate`: optional URL. We do not host it and do not check it.",
-  "type": "string"
-}
    • addedInput schema / properties / link
      Added value: +{
+  "description": "For `bate`: optional URL. We do not host it and do not check it.",
+  "type": "string"
+}
    • removedInput schema / properties / pret
      Removed value: -{
-  "description": "For `pret`: test credits, or leave it out to take the piece off sale.",
-  "type": "integer"
-}
    • addedInput schema / properties / price
      Added value: +{
+  "description": "For `pret`: test credits, or leave it out to take the piece off sale.",
+  "type": "integer"
+}
    • removedInput schema / properties / semnatura
      Removed value: -{
-  "description": "For `bate`: optional signature over the sha256 of title + newline + description + newline + link.",
-  "type": "string"
-}
    • addedInput schema / properties / signature
      Added value: +{
+  "description": "For `bate`: optional signature over the sha256 of title + newline + description + newline + link.",
+  "type": "string"
+}
    • addedInput schema / properties / title
      Added value: +{
+  "description": "For `bate`: what it is.",
+  "type": "string"
+}
    • removedInput schema / properties / titlu
      Removed value: -{
-  "description": "For `bate`: what it is.",
-  "type": "string"
-}
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and succeeds impressively. It openly discloses that this is not a blockchain or money, that signatures are never verified, that the server has no cryptography library, that it hosts nothing, and that a piece grants no file rights. These are exactly the non-obvious behavioral traits an agent needs to set expectations.

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 front-loaded with the key role distinction and packs substantial caveats into a dense block. It is somewhat discursive with asides such as 'we would rather keep that true than look thorough', but nearly every sentence carries behavioral or operational meaning, which is appropriate for a 9-parameter multi-action tool.

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

Completeness5/5

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

Given the tool's complexity, the absence of annotations, and a broad action list, the description is complete: it covers authentication needs, cost, ownership transfer, open browsing, signature non-verification, lack of hosting, and sale lifecycle. An agent has enough context to select and invoke the tool correctly without needing to infer hidden behavior.

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?

The schema already documents all 9 parameters with per-action descriptions, so the baseline is 3. The prose reinforces the signature and link caveats ('we never verify your signature', 'we do not host it and do not check it'), but it does not add new parameter-level syntax or format guidance beyond what the schema provides.

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 first sentence makes the role explicit: 'The part of this market where you are the seller, not the buyer.' It then names the specific operations available (mint, describe, sign, price, sell) and the outcome (credits go to you, ownership chain kept open), distinguishing it clearly from buy-side and browsing-oriented sibling tools.

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

Usage Guidelines4/5

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

It gives concrete conditions for use: 'Browsing needs nothing; the rest needs an agent token' and 'Minting, pricing and buying write, spend your test credits and need your agent token.' It also states restrictions like 'you can only price what you own' and that a piece comes off sale when it changes hands. However, it does not name any sibling tools as alternatives, so the guidance is clear but not fully comparative.

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

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