Skip to main content
Glama

Price of a search run

quote_search
Read-onlyIdempotent

The price in whole credits of running a ready search for leads leads (or of continuing a finished one for leads more): a low-high range; the start holds the high figure and charges what it really spends. Also the available balance. Show the price to the user and get a yes before run_search / continue_search, passing credits_high as confirm_credits. Free, changes nothing. [REST: GET /api/tasks/{id} (estimate.credits_by_target)]

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": {
      "task_id": "<task_id>"
    },
    "name": "quote_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadsNo
task_idYesThe search id (task id), e.g. from list_searches or create_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds real substance beyond them: the result is a low-high range, the returned start figure is charged at actual spend, and the available balance is included. The clause 'the start holds the high figure and charges what it really spends' is genuinely hard to parse and undercuts the otherwise useful disclosure.

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?

Compact and front-loads the price purpose before the workflow instruction, with no filler sentences. The nested parentheticals and the ambiguous range-ordering clause make it denser to parse than its length warrants.

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?

No output schema exists, so the description correctly describes the return shape (range endpoints plus available balance) and adds the cost-free, no-side-effect guarantee. It leaves mild ambiguity about exactly how `leads` is interpreted for a continuation, but covers what an agent needs to quote a price and gate the run.

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 50%: task_id is documented in the schema, but `leads` (default 20, range 1-100) has no schema description. The description supplies its meaning — number of leads to run, or additional leads when continuing a finished search — which is meaningful added context the schema alone lacks.

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?

States a specific verb+resource: returns the credit price of running (or continuing) a search for a given number of leads, plus available balance. It is clearly distinguishable from run_search/continue_search, which it references. The parenthetical 'or of continuing a finished one' muddies the single-purpose read slightly, keeping it from a 5.

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?

Explicitly prescribes the workflow: show the price to the user, get a yes, then call run_search / continue_search passing credits_high as confirm_credits. It names the alternatives and the exact hand-off parameter, so an agent knows when to call this rather than running the search directly.

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