Crawlwise

Estimate credit cost

estimate_cost

Read-onlyIdempotent

What an operation would cost this account, in credits. Never charges. Never creates a job. Does NOT reserve credits.

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": {
      "operation": "<operation>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

Name	Required	Description	Default
`units`	No	Pages, for a crawl. Ignored for an audit.
`operation`	Yes	audit for one page (audit_page), crawl for crawl_site.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026

addedInput schema / properties / operation / description

Added value: +"audit for one page (audit_page), crawl for crawl_site."

addedInput schema / properties / operation / enum
```
Added value: +[
+  "audit",
+  "crawl"
+]
```

addedInput schema / properties / units / description

Added value: +"Pages, for a crawl. Ignored for an audit."

removedInput schema / properties / url

Removed value: -{
-  "description": "Public http(s) URL.",
-  "type": "string"
-}

First observedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds important side-effect context: it never charges, never creates a job, and does not reserve credits. It does not cover edge cases such as invalid operations or whether the estimate can change, but it meaningfully supplements the structured annotations.

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 four short sentences with no wasted text. The key cost-estimate purpose and the no-side-effects constraint are front-loaded and easy to scan.

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 simple two-parameter read-only estimator with full schema coverage and rich annotations, the description is complete enough. It explains the return concept ('in credits') and explicitly rules out consequential side effects, which is the main behavioral risk for this 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%, including enum mapping for operation and units behavior for crawl versus audit. The description adds no parameter-specific syntax or semantics beyond what the schema already documents, so baseline 3 is appropriate.

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 states a specific verb and resource: estimating what an operation would cost this account in credits. It is clear enough to separate from execution tools like audit_page and crawl_site via 'Never creates a job,' but it does not explicitly name siblings such as get_credits or explain the distinction directly.

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?

Usage is implied: an agent should call this before an audit_page or crawl_site operation to check credit cost. However, the description does not explicitly say when to use this versus get_credits or when not to use it, leaving the routing guidance implicit.

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

All Crawlwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.