Portravo

View saved version →

---
name: portravo-prepare-takeoff
description: "Check trade availability and existing-credit cost, create an owned Portravo project, attach the actual plan PDF, and start an explicitly approved takeoff."
---

# Prepare a construction takeoff

Use the connected service at https://portravo.com/mcp through normal OAuth. If unavailable, preserve the selected plan and provide https://portravo.com/developers/mcp as the handoff. `get_profile` and `list_projects` identify the owned account and work.

Call `preflight_takeoff` without arguments for the live catalog, or with either proposed trades or a project_id, not both. Use `list_pricing_markets` for supported metro codes. Preserve automatic versus team-assisted scope, unresolved coverage and current cost; do not infer that every named trade runs automatically. Preflight neither reserves credits nor purchases anything.

Create a project only when requested, using `create_project` with an explicit selection returned by preflight and a stable idempotency_key. Keep that key after uncertainty. Attach only the user’s actual complete PDF with `attach_plan_pdf` and exactly one file source. Signed file transfer accepts up to 10 MiB; exact-byte inline base64 supports at most 32 KiB. Without an available transfer, use the returned owned project reviewUrl for browser upload up to 50 MiB. Never invent descriptors, truncate a plan or replace existing reviewed work.

Before `run_takeoff`, obtain any missing approval for the preflight selection and exact existing-credit ceiling. Pass confirmed_trades, max_credits and confirm_credit_use=true with a stable idempotency_key. Current maximum ceiling is three; the server rechecks actual cost. Do not infer one credit per trade or authorize billed overage. Changed cost/selection, insufficient balance or a credit guard needs resolution, not a larger ceiling or a new job.

Use `get_takeoff_status` after a running or uncertain response. Status reads never restart a run. Once ready, use `get_takeoff` to review actual source links, quantities, trade scope and unresolved work. Completion does not establish 95% whole-plan accuracy or a bid-ready estimate. Continue source and estimator review before pricing or export. Preserve errors and actual refund state instead of claiming a failed run succeeded.

View saved version →

---
name: portravo-review-estimate
description: "Recover an existing Portravo takeoff, inspect source-linked quantities and unresolved scope, and download a reviewed, priced estimate."
---

# Review and export an estimate

Use https://portravo.com/mcp through normal OAuth. Documentation: https://portravo.com/developers/mcp. Use `get_profile` and `list_projects` to find actual owned work. Resolve ambiguous project selection before accessing another project; preserve returned IDs and reviewUrl.

Use `get_takeoff_status` for asynchronous progress and interruption recovery. This reads state without advancing work. Do not rerun extraction to recover a status or satisfy a request to review an existing estimate.

Read `get_takeoff` when available. Preserve line IDs, source links, quantities, units, confidence, selected trades and human-review status. Explain unresolved lines and scope gaps, separating automated scope, team work and any unsupported trade. Compare against the actual plan when accessible; confidence and completed status do not prove completeness, correctness or 95% whole-plan accuracy. Do not fabricate source pages or claim all trades were measured.

Complete estimator review, assembly mappings and pricing in the owned project page. These MCP tools do not edit takeoff lines or override review status. `export_reviewed_estimate` succeeds only after every line is reviewed and the estimate is priced or final. On review_required, return its actual review link and remaining step; never bypass it or label a provisional artifact final.

After success, return the actual short-lived Excel download. If it expires, request a fresh export of the same reviewed project. A progress check or export request does not authorize a new takeoff, credit purchase or billed overage.

View saved version →

---
name: portravo-scope-questions
description: "Turn actual Portravo takeoff notes, unresolved lines and source gaps into an estimator checklist and draft clarification questions."
---

# Prepare scope questions from evidence

Use https://portravo.com/mcp through normal OAuth. Resolve the actual owned project with `list_projects`, recover running work with `get_takeoff_status`, and read `get_takeoff` when results exist. Connection help: https://portravo.com/developers/mcp. A request for clarification does not authorize a new extraction or credit use.

Trace each question to actual returned line notes, confidence, assembly mapping, source links or scope notes the user supplies. Preserve exact line IDs and source references. Low-confidence lines and missing mappings need review; no lines for a trade or page do not prove that scope was omitted. A page can be a title, note or detail sheet. Do not infer full sheet coverage from pages represented on quantity lines.

Prepare a checklist of assumptions to confirm, unmapped lines, unresolved or unsupported scope and specific drawing questions. Distinguish the absence of evidence from a verified omission. Use the user’s relevant trades and recipient role only when that information changes the questions. A general pre-bid checklist is possible without a connection, but label it general and do not attribute it to a plan you have not read.

Draft one concrete request-for-information question per material uncertainty, with actual reference, the question and what quantity or pricing decision depends on the answer. Do not accuse the designer, invent code requirements, fill missing quantities with typical scope or claim engineering/compliance conclusions. Drafts are for the user to review and send; this workflow sends nothing.

Return the owned project reviewUrl for estimator resolution. These tools do not add/fix lines or set review status. Do not rerun a takeoff merely to recover old scope notes, and do not promise whole-plan accuracy from selected lines.