RoofMeasure MCP

Official

by thegimmieapp

Overview Schema Source Related Servers Discussions Admin

Python

Remote

generate_roof_report

Create an EagleView-style roof measurement report for any address, delivering measurements and a saved Markdown file.

Instructions

Generate an EagleView-style roof measurement report (Markdown file) for an address. Returns JSON with the saved file path and a summary.

Args: address: Full property address. company: Company name stamped on the report. contact: Contact person shown on the report (optional). phone: Contact phone shown on the report (optional).

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": {
      "address": "<address>"
    },
    "name": "generate_roof_report"
  }
}

Input Schema

Name	Required	Default
`phone`	No
`address`	Yes
`company`	No	Stronghouse Solutions
`contact`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided; description reveals it saves a file and returns path/summary, but lacks details like file location, overwrite behavior, or external dependencies.

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?

Two informative sentences plus an args list. No redundant or irrelevant information. Well-structured.

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?

Has output schema, so return value description is sufficient. 1 required param, all explained. Minor lack of usage context prevents a 5.

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%, but description provides clear semantics for all 4 parameters (address, company, contact, phone), including optionality and defaults, adding value over schema.

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?

Clearly states verb 'generate', resource 'roof measurement report', format 'Markdown', and return value. Distinct from siblings like 'generate_xactimate_estimate' and 'measure_roof'.

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 on when to use this tool vs siblings. Does not indicate prerequisites or context for use.

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

Deploy Server