Computeback MCP — Agent rewards marketplace + CB Hire

Overview Schema Source Related Servers Discussions Admin

get_product_info

Query product knowledge for a business. Submit a question to retrieve relevant product context and information.

Instructions

Look up product knowledge for a business. Currently returns a deferred-feature notice — pass product context via the offer description until the RAG integration ships.

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": {
      "business_id": "<business_id>",
      "query": "<query>"
    },
    "name": "get_product_info"
  }
}

Input Schema

Name	Required	Description
`business_id`	Yes	The Computeback business id
`query`	Yes	The question or topic to look up
`top_k`	No	Max chunks to return (when implemented)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3May 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Fully discloses that the tool returns a deferred-feature notice and explains the temporary limitation. No annotations exist, so the description bears the transparency burden and meets it excellently.

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 concise sentences with zero wasted words. Front-loaded with the purpose, followed by critical behavioral and usage guidance.

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?

Adequately covers purpose, limitation, and workaround. No output schema exists, but the return type (notice) is implied. Could mention the structure of the notice, but not critical for a simple notification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents parameters. The description adds value by noting that 'top_k' is 'when implemented,' clarifying its current ineffectiveness – a useful semantic nuance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Look up product knowledge for a business.' However, it also reveals that the tool currently returns a deferred-feature notice rather than performing the lookup, slightly diminishing immediate utility.

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

Usage Guidelines5/5

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

Provides explicit guidance: 'pass product context via the offer description until the RAG integration ships.' This tells the agent when to use the tool and what to do instead, effectively differentiating it from sibling tools.

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