Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Estimate Tool

adataforseo.estimate

Estimates the cost of a DataForSEO job before it starts, using project currency, so you can review the budget and pass the same kind and options to start.

Instructions

Read-only. What a job would cost before it is started, in the project’s currency (US dollars with a DataForSEO account, euros when paying from the ai.artur.work balance, which only runs coverage, audit and difficulty); amount null means unknown and needs a manager approval. Pass the same kind and options to adataforseo.start_job after reviewing the estimate.

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": {
      "kind": "<kind>"
    },
    "name": "adataforseo.estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesJob kind
optionsNoJob options: crawl_pages, javascript, priority, depth, recheck, keywords; custom jobs also accept endpoint, tasks and variant. Budgets and permissions cannot be overridden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it declares read-only, explains currency is determined by account type, restricts euro-balance jobs to coverage/audit/difficulty, and defines null amount as unknown pending manager approval. It omits whether an estimate is binding or how long it stays valid, which matters before committing to a paid job.

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?

Reasonably tight and front-loaded with the safety signal (read-only) and the core definition before the currency caveat. The nested parenthetical about euro balance is dense but each clause carries information, and the closing sentence usefully points to start_job.

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?

For a two-parameter read tool with no output schema, the description covers cost semantics, currency rules, the null/approval path, and the handoff to start_job. Remaining gaps are minor: no indication of estimate validity window or response shape beyond the amount field.

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 meaning beyond it by tying the kind enum to currency eligibility (euros only cover coverage, audit and difficulty) and by flagging that budgets and permissions in options cannot be overridden.

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 and resource: returns what a job would cost before it is started. It is immediately distinguishable from adataforseo.start_job, which it explicitly frames as the follow-up action.

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?

Sets a clear usage context: call this before adataforseo.start_job, review the estimate, then pass the same kind and options. It also explains the null case routes to manager approval. It stops short of naming any alternative estimator (e.g. aimage.estimate) or stating when not to estimate at all.

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