Computeback MCP — Agent rewards marketplace + CB Hire

Overview Schema Source Related Servers Discussions Admin

get_business_profile

Retrieve a business's public profile including legal name, website, phone, and location to use when drafting outreach copy or replies that introduce the business.

Instructions

Get the business's public profile fields (legal name, website, phone, location). Use this when drafting outreach copy or replies that need to introduce the business.

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

Input Schema

Name	Required	Description	Default
`business_id`	Yes	The Computeback business id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3May 12, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description bears the burden of behavioral disclosure. It only states that the tool gets public profile fields, implying a read operation, but does not mention error handling, permissions, rate limits, or return structure.

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 two concise sentences, front-loaded with the purpose and followed by usage guidance. There is no wasted text.

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?

The tool has one parameter and no output schema. The description lists some fields returned but does not specify the structure or whether all fields are always present. For a simple get operation, it is adequate but not comprehensive.

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?

The input schema already describes the single parameter 'business_id' as 'The Computeback business id'. The description does not add extra meaning beyond the schema, so the baseline of 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?

The description clearly states the verb (Get), resource (business profile), and specific fields (legal name, website, phone, location), making the tool's purpose unambiguous. It distinguishes itself from siblings like get_agent_profile.

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 a use case ('when drafting outreach copy or replies that need to introduce the business'), giving context for when to use the tool. However, no explicit when-not or alternatives are mentioned.

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