Sky Solar

Start the roof plan PDF as a job (solar roof check)

roof_report_pdf_start

Read-only

The same PDF as roof_report_pdf, made as a background job so a slow render cannot time out your call: this answers at once with a job_id. The page's own report with its 3D picture takes 30 to 150 seconds to draw on the server. Then call roof_report_pdf_status with the job_id every 10 seconds until it says done (or failed, with the reason), and roof_report_pdf_file to get the file. If the page's report cannot be made in time you get the drawn version, and the status says so. The finished PDF is kept for 15 minutes under the random job_id; nothing else is stored.

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": {
      "link": "<link>"
    },
    "name": "roof_report_pdf_start"
  }
}

Input Schema

Name	Required	Description	Default
`link`	Yes	A solar roof check link (https://pv.skysolar.de/dachcheck/#d=…), as plan_roof, edit_roof or the solar roof check page gave it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already cover read-only, open-world, non-idempotent, and non-destructive behavior, while the description adds important operational context. It discloses the 30 to 150 second server render time, immediate job_id response, fallback to the drawn version, and 15-minute retention under a random job_id.

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 front-loaded with the key concept and then covers timing, polling, retrieval, fallback, and retention without filler. Every sentence contributes useful operational information.

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?

For an asynchronous job-start tool with no output schema, the description fully explains the lifecycle: immediate job_id, polling cadence, completion and failure states, file retrieval, fallback behavior, and retention window. Nothing essential for correct invocation 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% for the single link parameter, and the schema already explains the expected solar roof check link format. The description adds job-lifecycle context but no additional meaning about the link parameter itself, so the baseline score is appropriate.

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 states a specific verb and resource: starting the roof plan PDF as a background job. It explicitly distinguishes this tool from roof_report_pdf and from the status/file siblings, so an agent can tell what it is for.

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 gives explicit usage guidance: use this when a slow render could time out, then call roof_report_pdf_status every 10 seconds until done or failed, and then roof_report_pdf_file. The alternative non-job tool is named, and the polling sequence is fully specified.

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

All Sky Solar 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?