Atlasly

Get Job Status

get_job_status

Read-onlyIdempotent

Poll the status of an async Atlasly job (e.g. site package run). Returns current status, progress, and result summary when complete. Poll every 10–30 seconds until status is complete or failed. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.

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": "get_job_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job ID returned by run_site_package
`site_ref`	No	Canonical site_ref returned by any previous Atlasly tool. Pass it unchanged to chain the same resolved site into this call; address, search_area, or project_id will be filled from it when omitted.

Output Schema

Name	Required	Description	Default
`query`	No
`status`	Yes
`details`	No
`message`	No
`sources`	Yes
`headline`	Yes
`site_ref`	Yes
`retryable`	No
`error_code`	No
`atlasly_link`	Yes
`error_source`	No
`human_message`	No
`key_data_points`	Yes
`top_constraints`	Yes
`confidence_notes`	Yes
`executive_summary`	Yes
`next_best_actions`	Yes
`top_opportunities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description is consistent with all of them. Beyond that it discloses the polling cadence, the response payload shape (status, progress, result summary), and the chaining contract that site_ref is returned in every response. It does not describe failure/error behavior or backoff beyond the interval hint.

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?

Three front-loaded sentences with no filler: purpose and return payload first, polling cadence second, chaining contract last. Each sentence carries a distinct, actionable fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be fully specified, and the description still summarizes them. For a two-parameter async polling tool with a nested site_ref, the lifecycle and chaining story is covered; only failure-mode handling is left implicit.

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 site_ref schema text already explains "pass it unchanged to chain the same resolved site into this call." The description's chaining sentence largely restates that, though it does add the output-side fact that every response returns site_ref. With the schema doing the heavy lifting, the baseline 3 applies.

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 and resource ("poll the status of an async Atlasly job") and names the originating operation ("e.g. site package run"), which separates it cleanly from run_site_package in the sibling list. It also enumerates what comes back (status, progress, result summary), so an agent knows exactly what this tool yields.

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?

Gives concrete operational guidance that most definitions omit: poll every 10–30 seconds and stop when status is complete or failed. That is effectively a when-to-use and when-to-stop rule. It stops short of an explicit exclusion (e.g. do not call before a job is submitted, or what to do on failure), so it is not a full 5.

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

All Atlasly 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?