Skip to main content
Glama
Sign In

Sky Solar

by de.skysolar
OverviewDiscussionsAdmin

Get the finished 3D picture (solar roof check)

roof_picture_file
Read-onlyIdempotent

The finished picture of a roof_picture_start job, inside this answer as an embedded resource (image/png, or image/jpeg when the PNG was too big; base64) to save as a file; with inline: true as an image content block instead, which most clients show to you, so you can look at it. 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_picture_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
inlineNotrue: the picture as an image content block (image/png or image/jpeg), which most clients show to you, instead of an embedded resource to save as a file.
job_idYesThe job_id roof_picture_start gave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it explains the delivery mechanism precisely: an embedded resource with base64 data when the caller wants a file, versus an image content block when inline is set, plus the image/png → image/jpeg fallback when the PNG is oversized. That is exactly the behavioral context an agent cannot get from the annotations.

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?

A single dense sentence with no filler, and the key scoping constraint is stated at the end. The semicolon-chained clauses make it slightly harder to parse than a two-sentence split would be.

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?

There is no output schema, so the description must carry the return format — and it does, covering resource vs content block, encodings, MIME fallback, and the done-status gate. An agent has everything needed to call this correctly.

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 coverage is 100%, so both parameters are already documented in the schema, and the description's account of inline largely restates it. The only marginal addition is the framing of the resource-vs-content-block tradeoff, so the baseline 3 applies.

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 identifies the specific resource (the finished picture produced by a roof_picture_start job), which cleanly separates it from roof_picture_start and roof_picture_status. It is phrased as a noun fragment rather than a verb+resource clause, but the meaning is unambiguous.

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?

"Only when the status says done" gives an explicit precondition tied to the sibling roof_picture_status tool, which is real routing guidance. It omits what to do when the status is not done (poll status? error?), leaving that edge to inference.

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