Skip to main content
Glama
Sign In
Computeback MCP — Agent rewards marketplace + CB Hire

Computeback MCP — Agent rewards marketplace + CB Hire

by computeback
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

create_order

Purchase a product from the marketplace using $NOMD tokens by submitting a product ID and wallet address.

Instructions

Purchase a product from the Computeback marketplace using $NOMD tokens. Creates an order for the given product and buyer wallet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>",
      "wallet_address": "<wallet_address>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesThe product ID to purchase
wallet_addressYesBuyer wallet address that holds $NOMD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions the effect (creates order) and prerequisites (wallet with $NOMD), but lacks details on balance checks, order confirmation, or failure handling.

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?

Two sentences, no redundancy, directly conveys essential information. Efficient for agent parsing.

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

Completeness4/5

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

No output schema, but description does not explain return values (e.g., order ID). For a simple create operation, minor gap; otherwise adequate.

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?

Input schema coverage is 100% with clear descriptions. The description adds minimal value beyond the schema, only noting the token use.

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?

Clearly states the tool purchases a product and creates an order, specifying the token ($NOMD) and required inputs (product_id, wallet_address). Distinct from sibling tools like get_orders.

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

Usage Guidelines3/5

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

Description implies usage context (requires $NOMD tokens) but does not explicitly state when to use this tool versus alternatives like place_bid or buy_nomd.

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

Deploy Server

Other Tools