Skip to main content
Glama

Estimate credit cost

estimate_credits
Read-only

Estimate how many credits an operation will cost before you run it. Returns operation, count and estimated_credits. Free and read-only: it charges nothing and does not check your balance (use get_usage for that). Every operation currently costs 1 credit per address, and the estimate is an upper bound because cache hits, duplicates, malformed addresses and unresolved results are free.

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

Input Schema

NameRequiredDescriptionDefault
countYesHow many email addresses you plan to check.
operationYesThe tool you plan to run: send_decision for decide_send, verify_email for verify_email, verify_batch for create_verify_batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), yet the description still adds material behavior: it charges nothing, does not read the balance, costs 1 credit per address, and — importantly — the returned number is an upper bound because cache hits, duplicates, malformed addresses and unresolved results are free. That upper-bound caveat is exactly the kind of non-obvious trait annotations cannot express.

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 sentences, front-loaded with the purpose and return shape, then the routing hint, then the cost model. Every clause carries information an agent needs (cost, safety, upper-bound caveat); nothing is padding.

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?

There is no output schema, but the description names the three returned fields, so the return shape is covered anyway. For a two-parameter read-only estimation tool with full annotation coverage, the definition leaves nothing an agent needs to call it correctly.

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% and the enum-to-tool mapping is already in the schema, so the baseline is 3. The description earns an extra point by pinning down what `count` means economically ("1 credit per address") and by explaining why the estimate is an upper bound in terms of duplicate/malformed inputs — semantics the schema does not carry.

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?

"Estimate how many credits an operation will cost before you run it" gives a specific verb (estimate) and resource (credit cost) plus the temporal scope (pre-execution). It also enumerates the return fields (operation, count, estimated_credits) and explicitly separates itself from get_usage, so an agent can distinguish it from the balance-lookup sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the trigger condition ("before you run it") and routes the agent away with an explicit alternative: "does not check your balance (use get_usage for that)." The operation enum values are also mapped to their target tools inline, so the agent knows what to feed it for each downstream call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources