Skip to main content
Glama

Estimate credits

estimate
Read-onlyIdempotent

Preview the cost and potential errors of a billable API call before running it, returning minimum/maximum price, balance, and limit details without charging.

Instructions

Price a billable call without running it or charging for it (Clawifi API 1.7.0+). operation is one of fetch, scrape, extract, map, crawl, search_free or search_content; args are that operation's fields, for example {"url": "https://example.com"}, {"seed_url": ...} for crawl or {"query": ...} for the searches. Returns estimate {minimum, maximum, raises}, balance, would_402, would_429 and binding_limit; charged is 0.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
operationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds real behavioral context on top: "charged is 0", the version prerequisite (API 1.7.0+), and the fact that it predicts would_402/would_429 and a binding_limit before execution. The return-field enumeration is partly redundant with the output schema, which keeps it off a 5.

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?

Three dense sentences, front-loaded with the core guarantee (no run, no charge), then the contract, then the return payload. The parenthetical version note and inline JSON examples are compact and every clause carries information.

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?

An output schema exists so the return fields need not be spelled out, and the description still names them for orientation; the version gate, the zero-charge guarantee and the operation list cover what an agent needs to call it safely. The only gap is an authoritative mapping of args fields per operation, which it defers to the underlying operation tools.

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 0% with no enum on operation, so the description carries the burden and does most of it: it enumerates all seven accepted operation values and gives concrete args examples for url, seed_url and query. It falls short of specifying which fields belong to extract, map or search_content, leaving the agent to consult the sibling tool schemas.

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?

Opens with a precise verb and resource: "Price a billable call without running it or charging for it." That single clause separates it from every sibling (fetch, scrape, crawl, extract, map) because those actually execute the operation, while this only prices it.

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 condition for using this tool is clear — you want a cost preview before committing — and the operation vocabulary (fetch, scrape, extract, map, crawl, search_free, search_content) ties it directly to the sibling tools it estimates. It stops short of an explicit "do not use this to actually retrieve content" exclusion, so it is strong context rather than full routing guidance.

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