Skip to main content
Glama
Sign In

Sky Solar

by de.skysolar
OverviewDiscussionsAdmin

Get the finished roof plan PDF (solar roof check)

roof_report_pdf_file
Read-onlyIdempotent

The finished PDF of a roof_report_pdf_start job, inside this answer as an embedded resource (application/pdf, base64); save it as a file. Only when the status says done.

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": {
      "job_id": "<job_id>"
    },
    "name": "roof_report_pdf_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id roof_report_pdf_start gave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive local read. The description adds important behavioral detail beyond that by saying the result appears as an embedded resource with MIME type application/pdf and base64 content, and that the agent should save it as a file. It could say more about what happens when the job is not done, but the core return behavior is disclosed.

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 tightly packed sentence with the main action and resource front-loaded. The parenthetical clarifies the embedded resource format without wasting space, and the precondition is placed at the end as a clear gate.

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 a simple one-parameter retrieval tool with rich annotations and no output schema, the description covers the prerequisite, the return format, and the expected action of saving the file. An agent has enough information to invoke it correctly without needing additional structured output details.

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%, and the schema already explains that job_id is the identifier produced by roof_report_pdf_start. The description reinforces that the job is a roof_report_pdf_start job but does not add format, validation, or lookup semantics beyond the 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?

The description states a specific verb and resource: get the finished PDF of a roof_report_pdf_start job. It distinguishes the output from related sibling concepts by describing it as an embedded application/pdf resource that must be saved as a file, and it ties the call to a completed start job.

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

Usage Guidelines4/5

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

The description gives a clear precondition: call this only when the status says done. It does not explicitly name the alternative tool to use when the status is not done, but the sequencing with roof_report_pdf_start and the status check is implied well enough for an agent to act correctly.

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

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