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

get_product

Retrieve complete product details including $NOMD price, USD value, vendor, and description from Computeback marketplace by providing a product ID.

Instructions

Get full details for a specific product in the Computeback marketplace, including $NOMD price, USD value, vendor, and description.

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>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesThe product ID to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It describes what the tool returns but does not disclose error behavior, idempotency, or auth requirements. Basic transparency for a read operation but sparse.

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?

One clear sentence, no fluff, front-loaded with purpose and outputs.

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

Completeness3/5

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

Given low complexity (1 param, no output schema), description is fairly complete. However, lacks differentiation from sibling get_product_info and no mention of error handling.

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 has 100% coverage for product_id with description 'The product ID to look up'. Tool description adds no param-level details beyond the schema, so baseline 3 is appropriate.

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 'Get full details' and resource 'product in Computeback marketplace' with specific fields listed ($NOMD price, USD value, vendor, description). Differentiates from siblings like get_product_info by implying this is for a specific product by ID.

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 usage (when you have a product ID) but no explicit when-not-to-use or alternative guidance. With siblings like get_product_info and search_products, some clarification would help.

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