Perch Data

perchpermits/kitchen-floor-plan-takeoff

perchpermits--kitchen-floor-plan-takeoff

Destructive

This tool calls the Actor "perchpermits/kitchen-floor-plan-takeoff" and retrieves its output results. Actor description: Turn a short JSON room spec into a dimensioned floor plan (SVG), a cabinet and appliance takeoff (CSV), and quote-ready totals. No CAD, no rendering, seconds per plan.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`spec`	No	REQUIRED The room and everything in it. See the README for the full schema. Minimum: `room` {width, depth, height} and one `cabinet_runs[]` entry with `wall`, `start`, `end`, and `appliances[]` of {type, at, width}. Walls are north/south/east/west; positions run left to right along each wall as seen from inside the room. Example values: {"title":"Galley kitchen","room":{"width":4.2,"depth":3.6,"height":2.7},"style":{"counter":"white_quartz"},"windows":[{"wall":"north","u0":1.75,"u1":2.85,"z0":1.05,"z1":2}],"openings":[{"wall":"south","u0":0.4,"u1":1.3}],"cabinet_runs":[{"wall":"north","start":0,"end":4.2,"uppers":true,"appliances":[{"type":"fridge","at":0,"width":0.9},{"type":"sink","at":1.9,"width":0.8},{"type":"dishwasher","at":2.7,"width":0.6},{"type":"range","at":3.3,"width":0.76}]}],"island":{"x":2.1,"y":1.5,"width":2,"depth":0.9,"pendants":2,"stools":3}}
`title`	No	Printed on the plan. Defaults to `spec.title` or `spec.name`.
`units`	No	Every length in `spec` is read in these units and converted to metres internally. Output widths are always in inches, summary totals in feet. Example values: "m"	m
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`validateOnly`	No	Check the spec and return errors and warnings without building anything. Not charged.

Output Schema

TableJSON Schema

Name	Required	Description
`runId`	Yes	Actor run ID
`stats`	No	Run statistics
`status`	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
`actorId`	Yes	Stable Apify Actor ID from the run record
`summary`	Yes	Past-tense summary of the run state
`exitCode`	No	Actor process exit code; populated for terminal states (especially FAILED)
`nextStep`	Yes	One primary follow-up action with identifiers interpolated
`storages`	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
`actorName`	No	"username/actor-name"
`startedAt`	No	ISO timestamp when the run started
`finishedAt`	No	ISO timestamp when the run finished (terminal states only)
`statusMessage`	No	Pass-through from Apify run.statusMessage
`apifyConsoleUrl`	No	Personalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint false, openWorldHint true, and destructiveHint true, covering safety. The description adds the note 'No CAD, no rendering, seconds per plan,' offering a performance expectation. It does not elaborate on side effects or authentication, but annotations already carry that burden, so a 3 is appropriate—the description adds some behavioral context but not much.

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?

The description is two sentences plus the Actor description, which is concise and front-loaded with the Actor call and purpose. It avoids verbosity, though the first sentence could have been merged with the purpose, but overall it remains succinct and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives output types (SVG, CSV, totals) but does not explain how to interpret results, handle errors, or cover edge cases. Given that an output schema exists and the input schema is well-documented, the tool is mostly complete, but some context about the Actor's limitations or prerequisites is missing.

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?

Schema description coverage is 100%; all parameters have detailed descriptions in the schema itself. The tool description adds nothing about parameters, so the baseline of 3 applies. The schema provides the full semantic weight for parameters like `spec`, `units`, `waitSecs`, and `validateOnly`.

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 the tool calls a specific Actor and then reproduces the Actor's purpose: turning a JSON room spec into an SVG floor plan, CSV cabinet takeoff, and quote-ready totals. The verb 'calls' and the concrete output types give clear intent. It doesn't explicitly differentiate from sibling tools, but the name and the Actor description make it obvious this is for kitchen floor plan takeoffs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description only says it calls an Actor and retrieves results, with no mention of conditions, prerequisites, or exclusions. For example, it doesn't say when not to use it or that it is specifically for kitchen plans rather than other plan types.

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

All Perch Data 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.