Skip to main content
Glama
Kentucky-ai

opentakeoff-mcp

by Kentucky-ai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

load_plan

Open a plan PDF in the local takeoff engine to begin a takeoff session. Set merge to add the document to existing sheets, preserving scales, conditions, and shapes for multi-file bid sets.

Instructions

Open a plan PDF from disk. Default: replace the whole session (previous documents, scales, conditions, and shapes are cleared). merge: true ADDS the document to the working set instead (#152) — a bid set is plans + schedule + addenda, not one PDF — keeping every scale, condition, and shape; sheet keys carry file names so documents never collide, the sheet graph spans the whole set (resolve_tag can chain a plan tag on one file to a schedule row in another), and the marked set covers every worked sheet. Re-loading an already-merged file is refused — reload = replace, deliberately. Returns file, files, page_count, and one entry per sheet. The loaded sheets also become browsable resources (takeoff://sheets). Coordinates are image px at render scale 2.0: PDF pt × 2, origin top-left, y down (the browser canvas's native space). Sheet payloads carry dims in both px and pt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to a plan PDF on disk
mergeNotrue = ADD this document to the working set, keeping all existing work (merge into an empty session is just a load)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesThe document just loaded (basename)
noteYes
filesYesEvery document in the working set, load order (#152 — one entry unless merge was used)
sheetsYesEVERY sheet in the working set, not just the file loaded by this call
page_countYesTotal sheets across the working set

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.1.9
    • addedInput schema / properties / merge
      Added value: +{
+  "description": "true = ADD this document to the working set, keeping all existing work (merge into an empty session is just a load)",
+  "type": "boolean"
+}
    • addedOutput schema / properties / file / description
      Added value: +"The document just loaded (basename)"
    • addedOutput schema / properties / files
      Added value: +{
+  "description": "Every document in the working set, load order (#152 — one entry unless merge was used)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / page_count / description
      Added value: +"Total sheets across the working set"
    • addedOutput schema / properties / sheets / description
      Added value: +"EVERY sheet in the working set, not just the file loaded by this call"
    • changedOutput schema / required
      Previous value: -[
-  "file",
-  "page_count",
-  "sheets",
-  "note"
-]New value: +[
+  "file",
+  "files",
+  "page_count",
+  "sheets",
+  "note"
+]
  2. Addedv0.1.5
  3. Removedv0.1.4
  4. Addedv0.1.3
  5. Removedv0.1.2
  6. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels: it discloses the destructive default (clears session), the merge behavior, the refusal condition, the return payload, coordinate system details, and the conversion to browsable resources. This is a comprehensive safety/behavioral profile.

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?

The description is a single dense paragraph but logically organized: action, default behavior, merge variant, edge case, return values, resources, and coordinate system. Every sentence adds necessary information with no filler, achieving conciseness through purposeful density.

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?

Given the tool's moderate complexity and absence of annotations, the description covers everything an agent needs: the two modes, re-load restriction, return fields, coordinate transformation, and resource availability. It is fully sufficient for correct invocation and interpretation.

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?

The schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds meaningful context beyond the schema by elaborating on the default behavior, the meaning of merge:true, and the edge case of merging into an empty session, increasing clarity for parameter usage.

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?

The description opens with a clear verb+resource ('Open a plan PDF from disk') and immediately clarifies the default replacement behavior versus merge mode. This distinguishes it from sibling tools that operate on already-loaded sheets or produce analyses.

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 explicitly contrasts the default replace-all behavior with merge:true for adding to a working set, explains the bid-set use case, and states that re-loading an already-merged file is refused. This gives clear when-to-use and when-not-to-use guidance, including a concrete scenario.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kentucky-ai/opentakeoff'

If you have feedback or need assistance with the MCP directory API, please join our Discord server