Skip to main content
Glama

MarketAIVerse

by com.marketaiverse
OverviewDiscussionsAdmin

Practise buying, with money that is not money

sandbox

A practice market so you can write and test your buying code today, before any real payment path exists. You get test credits that cannot be bought, cannot be converted, and deliver nothing — every reply says TEST in the amount and in the currency, and the delivery field is deliberately empty so your code learns the shape without believing it owns anything. Prices are the same as the real ones, so nothing rescales later. Needs an agent identity: POST /api/v1/agents with {"name": "..."}, then Authorization: Bearer . Writes, but only inside the sandbox: no real money moves and no real goods change hands. That is the point of it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFor `buy`: the id of the thing, e.g. `manuale`.
actionNopurse (how many test credits you have), buy (practise a purchase), or receipts (what you practised so far). Default: purse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"punga (how many test credits you have), cumpara (practise a purchase), or chitante (what you practised so far). Default: punga."New value: +"purse (how many test credits you have), buy (practise a purchase), or receipts (what you practised so far). Default: purse."
    • changedInput schema / properties / id / description
      Previous value: -"For `cumpara`: the id of the thing, e.g. `ghid`."New value: +"For `buy`: the id of the thing, e.g. `manuale`."
  2. Changed2 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
+  "description": "punga (how many test credits you have), cumpara (practise a purchase), or chitante (what you practised so far). Default: punga.",
+  "type": "string"
+}
    • removedInput schema / properties / ce
      Removed value: -{
-  "description": "punga (how many test credits you have), cumpara (practise a purchase), or chitante (what you practised so far). Default: punga.",
-  "type": "string"
-}
  3. Added

TDQS

A4.5/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 does so thoroughly. It discloses that the tool writes but only inside the sandbox, that credits cannot be bought/converted/deliver nothing, that replies say TEST in amount and currency, and that the delivery field is deliberately empty. It also states the authentication requirement and explicitly says no real money moves and no real goods change hands.

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 front-loaded with the core purpose and then efficiently covers credits, response characteristics, pricing, auth, and safety. Every sentence adds value; there is no filler or repetition. The structure moves from purpose to behavior to integration requirements in a logical order.

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 no output schema and no annotations, this description is remarkably complete. It explains response shape ('TEST' in amount/currency, empty delivery field), authentication setup, parameter meanings, and the sandbox's safety boundaries. An agent has everything needed to invoke it safely and understand the result.

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 description coverage is 100%, so the schema already documents both parameters. The description adds meaningful context about what 'purse', 'buy', and 'receipts' mean through the practice-market framing, but it does not substantially go beyond the schema's parameter descriptions. This is the appropriate baseline for full schema coverage.

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 this is a practice market for writing and testing buying code before a real payment path exists. It emphasizes 'TEST' amounts and empty delivery fields, clearly distinguishing it from real purchase or payment tools among the siblings. The verb+resource framing ('practice market', 'write and test your buying code') is specific and unambiguous.

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?

The description provides clear context for when to use the tool: 'today, before any real payment path exists' and for testing code without real money or goods. While it does not explicitly name sibling alternatives or enumerate when not to use it, the practice-vs-real contrast gives sufficient usage direction.

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