Skip to main content
Glama

Start a portfolio estimate

estimate_portfolio
Read-onlyIdempotent

Price many buildings in one job (up to 500 sites, or the key's batch limit). Returns a job id at once; poll get_portfolio_job until status is done. Each site is billed as one request. defaults applies to every site and any site may override a field; a site takes the same fields as estimate_plan. Never add an incentive whose counts_toward_roi is false (paused, waitlisted, closed) or that is contingent or competitive into any total; show every stated condition beside its incentive; name incentives by their ref (e.g. US12c). Amounts are guidance to be confirmed with the grantor.

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": {
      "sites": "<sites>"
    },
    "name": "estimate_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitesYes
defaultsNo

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and non-destructive, yet the description still adds material behavior: asynchronous job creation with a returned job id, a polling protocol, per-site billing ("Each site is billed as one request"), and a batch cap. It also carries domain correctness rules — never fold non-ROI, contingent or competitive incentives into totals, show stated conditions, name incentives by ref — which are the kind of constraint an agent could not infer from any structured field.

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?

Front-loaded with the core action and scale, then the async protocol, then the precedence rule, then domain constraints — a sensible ordering with essentially no filler sentences. It is dense and the incentive/ROI rules arrive as a run-on cluster, but each clause carries a distinct constraint.

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?

Output schema exists, so return values need no explanation, and the description correctly spends its space on invocation mechanics (async polling, billing, batch limit) and result-integrity rules instead. Gaps remain around failure behavior — what happens if a site in the batch is invalid or the job fails partway — and around any authorization or quota prerequisites beyond the batch limit.

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% and the item objects are free-form (additionalProperties: true), so the description carries the full burden. It explains that sites is a list of site objects, that each site accepts the same fields as estimate_plan, and crucially defines the precedence rule that `defaults` applies to every site while any site may override a field. What it omits is any hint of the actual required fields inside a site object, deferring entirely to the sibling tool.

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 — "Price many buildings in one job" — plus an explicit scale bound (up to 500 sites or the key's batch limit), which distinguishes it cleanly from the single-plan sibling estimate_plan. The paired mention of get_portfolio_job for polling makes the async shape of the call unmistakable.

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?

Gives clear operational context: call it, get a job id back immediately, then poll get_portfolio_job until status is done, and note that each site mirrors estimate_plan's fields. It does not explicitly say when to use estimate_plan instead of this tool (single site vs. many), so the routing guidance is implied rather than stated.

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