Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Estimate a list

estimate_list
Read-onlyIdempotent

Rows, cost in credits and balance after, for a list of N rows of a search (up to 50,000). Tell the user the cost, then send "cost" as maxCredits to create_list with the same search, rows and withEmail. In a rarely searched area it returns kind "zone": the list fills itself after creation (create_list with maxCredits ≥ zoneEstimate.creditCap).

Free.

Same call as POST /api/v1/search/estimate of the REST API.

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": {
      "search": "<search>"
    },
    "name": "estimate_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoRows wanted in the list (default 500, at most 50000).
searchYesThe search, as returned by POST /categories/suggest (field "search"). Send it back as is, edited if needed. The "search" object returned by suggest_categories (target, area, filters, sort), sent as is or edited; its full schema is the "search" input of count_search. An invalid search is refused with invalid_request and the fields to fix.
withEmailNoTrue: a list of places WITH an email address (found addresses first, then guessed and checked ones, each address checked at 1 credit). False: the email filter is removed. Absent: the search as is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it discloses genuinely useful behavior: the call is free, email addresses are checked at 1 credit each, and zone results cause the list to fill itself after creation. It stops short of describing latency, pagination of results, or failure modes other than the invalid search refusal hinted at in the schema.

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?

Dense but front-loaded, with the estimate purpose first and the follow-up action second; the one-word 'Free.' sentence carries real information. The zone clause is crammed into a single sentence with nested parentheses, which costs some readability.

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?

With no output schema, the description carries the return-value burden and does it: it names rows, cost in credits, balance after, and the 'zone' kind with zoneEstimate.creditCap. Combined with a fully described three-parameter schema and readOnly annotations, an agent has what it needs to call and interpret it.

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 the schema cannot: the returned 'cost' becomes maxCredits on create_list, and rows/search/withEmail must be replayed identically. It reiterates the 50,000 cap already in the schema, which earns no extra credit.

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 concretely that it returns rows, credit cost and post-call balance for a list of N rows of a search, capped at 50,000, which makes the resource and output unmistakable. It does not lead with a verb ('estimate'), but the opening clause and the create_list hand-off make the function distinguishable from count_search and create_list.

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?

It gives an explicit workflow: show the cost to the user, then pass 'cost' as maxCredits to create_list with the same search, rows and withEmail. It also names a separate condition (a rarely searched area returning kind 'zone') and tells the agent what to do in that case (create_list with maxCredits >= zoneEstimate.creditCap).

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

All Primavera toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources