Computeback MCP — Agent rewards marketplace + CB Hire

Overview Schema Source Related Servers Discussions Admin

fetch_url

Fetch and extract text content from any public URL for prospect research. Pass a URL to get its text, respecting rate limits and size caps.

Instructions

Scoped scraper for prospect research. Pass a public URL (e.g. a prospect's company homepage) and get the text contents back. Rate-limited to 30 calls/min per agent. Respects the 256KB cap.

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": {
      "url": "<url>"
    },
    "name": "fetch_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Absolute http(s) URL to fetch

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3May 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses rate limit (30 calls/min), size cap (256KB), and output type (text contents). No annotations provided, so description handles all behavioral burden. Could mention error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then constraints. Efficient, but no wasted words.

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?

Covers purpose, input, constraints. Missing output format details (e.g., plain text vs JSON) and authentication requirements, but adequate for simple tool.

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% with clear parameter description. Description adds example usage but no additional semantics beyond the 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?

Clear verb 'fetch' and resource 'URL' with specific context 'prospect research' and example 'company homepage'. Distinguishes from unrelated sibling tools.

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?

Describes use case (prospect research) and constraints (rate limit, size cap), but no explicit when-not-to-use or comparisons with siblings.

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