Portravo Construction Takeoff

Read takeoff progress

get_takeoff_status

Read-onlyIdempotent

Read an owned project and its latest asynchronous takeoff progress, completion limitations and review link. Never advances or restarts a run, uses credits or changes billing. Poll this tool after run_takeoff returns a running result.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_takeoff_status"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes

Output Schema

Name	Required	Description	Default
`run`	Yes
`projectId`	Yes
`reviewUrl`	Yes
`projectStatus`	Yes
`reviewRequired`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavioral context: it never advances or restarts a run, never uses credits, never changes billing. That is exactly the side-effect disclosure an agent needs before polling in a loop.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, no waste, with the read scope front-loaded and the polling instruction placed last where an agent will look for next-action guidance.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile; the description still adds the polling workflow and cost-neutrality facts. Complete for a single-purpose status tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter with 0% schema description coverage, so the description must carry meaning; it only implies ownership ('an owned project') without explaining project_id format or where it comes from. The pattern/length constraints in the schema are syntactic, not semantic, so this is a baseline-level pass.

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 (Read) plus resource (an owned project and its latest asynchronous takeoff progress, completion limitations and review link), and implicitly separates itself from run_takeoff by being the read/poll counterpart. An agent can tell what it returns without opening the schema.

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?

Gives an explicit trigger condition: 'Poll this tool after run_takeoff returns a running result,' which names the sibling that precedes it and the state that selects this tool. Nothing is left to inference.

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

All Portravo Construction Takeoff tools Inspect

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

Need Help?