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

search_products

Search the marketplace for products available with $NOMD tokens. Filter by category, keyword, or sort order to find compute, voice, memory, and more.

Instructions

Search the Computeback rewards marketplace for products purchasable with $NOMD tokens. Filter by category, keyword, or sort order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category slug
queryNoFree-text search query
sortNoSort order for results

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 carries full burden. Discloses read-like behavior (search) but does not mention pagination, limit on results, or any side effects. Adequate but not rich.

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, front-loaded with purpose, no extraneous words. Efficient and easy to parse.

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?

For a simple search tool with 3 optional parameters and no output schema, the description sufficiently covers what the tool does. Missing mention of pagination or result structure, but not critical for basic understanding.

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%, baseline 3. Description lists filters (category, keyword, sort order) matching parameters. Reinforces schema descriptions but adds no new semantics beyond what is already in the input schema.

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?

Description clearly states verb 'Search', resource 'products in Computeback rewards marketplace', and constraint 'purchasable with $NOMD tokens'. Differentiates from siblings like get_product/get_product_info which are for individual product retrieval.

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?

Implied use case (searching products by filters) but no explicit guidance on when to use this tool over alternatives like get_categories or get_product. No exclusions or when-not-to-use mentioned.

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