RoofScope MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROOFSCOPE_TOKEN | Yes | Your account's Scope API Token (My Details → Third-Party). Required. | |
| ROOFSCOPE_API_KEY | Yes | The API key Scope Technologies issued you. Required. | |
| ROOFSCOPE_SOURCE_ID | No | Only if Scope Technologies assigned you a source id. | |
| ROOFSCOPE_ALLOW_ORDERS | No | Set to true to let the assistant place paid orders. Off by default. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_roofscope_scopesA | Find RoofScope reports ("scopes") on the account whose address or name contains the search text. Returns each one's scopeId, orderId, product, status (Ordered, Completed, Unfunded…), whether it is on hold and why, and the order date. Leave query empty for the most recent. Use the scopeId with get_roofscope_scope for the measurements. |
| get_roofscope_scopeA | One RoofScope report's measurements. For roof products: total roof area (in squares) by slope bucket and pitch, perimeter, eaves, rakes, ridges, hips, valleys, step and headwall flashing, and every plane per structure. For GutterScope / RoofScopePlus: gutter and downspout length, end caps and elbows. For SidingScope: siding area, wraps, windows and doors. Plus links to the PDF (and DXF/DWG where there are any). An unfinished or held report comes back as its status instead. |
| get_roofscope_pricesA | What each RoofScope report costs on this account, by product, property type and size band (e.g. "RoofScope-Residential-Greater Than 50 SQ": 69.95). |
| get_roofscope_delivery_optionsA | The extra charge for standard and rush delivery, per RoofScope product and size band. |
| check_roofscope_connectionA | Whether RoofScope accepts this server's API key and the account's Scope API Token, and whether ordering is turned on. Use it when another RoofScope tool fails, or to confirm the setup. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: search (list/find reports), get (measurements for one report), prices, delivery options, and a connection diagnostic. The search/get pairing is clearly delineated by the descriptions (query vs. scopeId), and prices vs. delivery charges cannot be confused.
All five names follow a consistent snake_case verb_noun pattern with a uniform roofscope prefix: search_roofscope_scopes, get_roofscope_scope, get_roofscope_prices, get_roofscope_delivery_options, check_roofscope_connection. No mixing of conventions.
Five tools is well-scoped for a read-only RoofScope data integration; each tool earns its place (discovery, detail, pricing, delivery, health check) with no redundancy or padding.
The surface covers discovery, measurement retrieval, pricing, delivery costs, and connection validation, which handles most read-only workflows. However, ordering a report is alluded to (check_roofscope_connection reports whether ordering is on) yet no order/create tool is exposed, leaving a minor lifecycle gap.