Skip to main content
Glama
RapierCraft

alterlab-mcp-server

by RapierCraft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alterlab_estimate_cost

Estimate scraping cost for a URL before scraping, with no credits charged. Shows predicted anti-bot tier, per-request cost, and confidence.

Instructions

Preview the cost of scraping a URL before committing — no credits charged. Returns the predicted anti-bot tier, estimated cost per request, and confidence level. Call this before scraping protected or unfamiliar sites to avoid surprises. Tier 1 (curl): $0.0002. Tier 2 (http): $0.0003. Tier 3 (stealth): $0.002. Tier 3.5 (lightjs): $0.0025. Tier 4 (full browser): $0.004. Tier 5 (captcha solver): $0.02. Use render_js, use_proxy, screenshot, generate_pdf, ocr and method to see how options affect cost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ocrNoInclude the OCR add-on (+$0.001)
urlYesURL to estimate scraping cost for
modeNoScraping modeauto
methodNoHTTP method. POST requests cost 1.5x the base tier price.
formatsNoOutput formats to include in the estimate. Passed to the API but does not currently affect the cost estimate — the endpoint uses URL-pattern heuristics only. 'markdown' is best for LLM consumption. 'json_v2' returns a structured section tree (headings + content blocks). 'rag' returns chunked text optimized for retrieval-augmented generation. 'raw' returns the raw response body without extraction. 'content' returns body_markdown + content_hash + images + links for AI/KB pipelines.
render_jsNoEnable JS rendering (forces Tier 4 minimum, $0.004 — no separate add-on charge)
use_proxyNoInclude premium proxy cost (+$0.0002)
screenshotNoInclude the screenshot add-on (+$0.0002)
generate_pdfNoInclude the PDF add-on (+$0.0004)
use_own_proxyNoPrice the request with your own proxy integration (20% BYOP discount)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.9.0
    • changedInput schema / properties / formats / description
      Previous value: -"Output formats to include in the estimate. Passed to the API but does not currently affect the cost estimate — the endpoint uses URL-pattern heuristics only. 'json_v2' returns a structured section tree. 'rag' returns chunked text for retrieval-augmented generation. 'content' returns body_markdown + content_hash + images + links. 'raw' returns the response body byte-for-byte with no transformation."New value: +"Output formats to include in the estimate. Passed to the API but does not currently affect the cost estimate — the endpoint uses URL-pattern heuristics only. 'markdown' is best for LLM consumption. 'json_v2' returns a structured section tree (headings + content blocks). 'rag' returns chunked text optimized for retrieval-augmented generation. 'raw' returns the raw response body without extraction. 'content' returns body_markdown + content_hash + images + links for AI/KB pipelines."
    • addedInput schema / properties / generate_pdf
      Added value: +{
+  "description": "Include the PDF add-on (+$0.0004)",
+  "type": "boolean"
+}
    • addedInput schema / properties / method
      Added value: +{
+  "description": "HTTP method. POST requests cost 1.5x the base tier price.",
+  "enum": [
+    "GET",
+    "POST"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / ocr
      Added value: +{
+  "description": "Include the OCR add-on (+$0.001)",
+  "type": "boolean"
+}
    • addedInput schema / properties / render_js / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "const": "auto",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / render_js / description
      Previous value: -"Enable JS rendering (forces Tier 4 minimum — no separate add-on charge)"New value: +"Enable JS rendering (forces Tier 4 minimum, $0.004 — no separate add-on charge)"
    • removedInput schema / properties / render_js / type
      Removed value: -"boolean"
    • addedInput schema / properties / screenshot
      Added value: +{
+  "description": "Include the screenshot add-on (+$0.0002)",
+  "type": "boolean"
+}
    • addedInput schema / properties / url / maxLength
      Added value: +2083
    • addedInput schema / properties / use_own_proxy
      Added value: +{
+  "description": "Price the request with your own proxy integration (20% BYOP discount)",
+  "type": "boolean"
+}
    • changedInput schema / properties / use_proxy / description
      Previous value: -"Include premium proxy cost (+1 credit)"New value: +"Include premium proxy cost (+$0.0002)"
  2. Changed1 schema field changedv1.8.0
    • changedInput schema / properties / formats / description
      Previous value: -"Output formats to include in the estimate. Affects cost prediction accuracy. 'json_v2' returns a structured section tree. 'rag' returns chunked text for retrieval-augmented generation. 'content' returns body_markdown + content_hash + images + links. 'raw' returns the response body byte-for-byte with no transformation."New value: +"Output formats to include in the estimate. Passed to the API but does not currently affect the cost estimate — the endpoint uses URL-pattern heuristics only. 'json_v2' returns a structured section tree. 'rag' returns chunked text for retrieval-augmented generation. 'content' returns body_markdown + content_hash + images + links. 'raw' returns the response body byte-for-byte with no transformation."
  3. First observedv1.5.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that no credits are charged, that it returns a predicted anti-bot tier, cost, and confidence, and it enumerates the exact per-tier pricing and add-on effects on cost — the key behavior an agent needs to interpret results.

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?

Purpose is front-loaded in the first clause, and every subsequent sentence (the tier price table, the options hint) is cost-relevant reference material, not padding. The price enumeration is dense but each line maps directly to behavior the caller must interpret.

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

Completeness5/5

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

For a 10-param tool with no output schema and no annotations, the description compensates fully by naming the return fields (tier, cost, confidence) and the zero-charge guarantee, so an agent can invoke and interpret it without further context.

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 baseline is 3, but the description adds value beyond the schema by listing tier prices referenced by the option params and by instructing which params to use to see cost effects (render_js, use_proxy, screenshot, generate_pdf, ocr, method). It stops short of explaining each param's syntax, hence 4.

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?

States a specific verb+resource+scope: 'Preview the cost of scraping a URL before committing — no credits charged.' It is immediately distinguishable from the many action siblings (alterlab_scrape, alterlab_batch_scrape, etc.) because it is explicitly a non-executing preview.

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?

Gives a clear when-to-use rule: 'Call this before scraping protected or unfamiliar sites to avoid surprises.' It does not state a when-not condition (e.g. no need for already-known cheap sites), but no competing estimate sibling exists, so the routing guidance is effectively complete.

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