Sky Solar

Status of a 3D picture job (solar roof check)

roof_picture_status

Read-onlyIdempotent

Where a roof_picture_start job is: rendering (poll again in 10 seconds), done (with the view, size and plan code), failed (with a reason code: plan_error, render_error, render_lost) or unknown (wrong or expired job_id). A tool error here means the call itself failed, not the job.

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_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The job_id roof_picture_start gave.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, yet the description adds real value: the polling interval, the meaning of each state, the failure reason codes, and the crucial distinction that a tool error means the call failed rather than the job. That last point is behavioral context an agent could not infer from annotations or schema.

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 front-loaded sentence with a compact state enumeration; nearly every clause carries information. The parenthetical nesting is slightly dense but readable, and nothing is filler.

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 carries the burden of describing return values, and it does: done carries view, size and plan code; failed carries a reason code with the enumerated values. Combined with the error-vs-job-failure note, an agent has everything needed to call and interpret this tool.

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 100%, so job_id format and provenance are already documented. The description still adds semantic meaning by noting that an 'unknown' status corresponds to a wrong or expired job_id, telling the agent that job IDs have a lifetime — information not present in 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?

States a specific verb+resource: it reports where a roof_picture_start job stands, and enumerates all four terminal states. This clearly distinguishes it from the sibling roof_report_pdf_status, which covers a different job family.

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?

Usage is clearly implied as the poll step of the roof_picture_start workflow, and the description even specifies the cadence ('poll again in 10 seconds' while rendering). It does not explicitly state what to do after 'failed' (e.g., restart vs. give up), so it falls short of full when/when-not guidance.

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?