RQM Robotics Jobs

get cloud motion result

get_cloud_motion_result

Read-onlyIdempotent

Read owner-scoped motion result. Modeled sphere validation is not physical safety certification or permission to actuate.

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

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Output Schema

Name	Required	Description	Default
`job_id`	Yes
`artifact`	Yes
`quote_id`	Yes
`request_hash`	Yes
`capability_id`	Yes
`catalog_digest`	Yes
`claim_boundary`	Yes
`reservation_id`	Yes
`rqm_account_id`	Yes
`schema_version`	Yes
`tariff_version`	Yes
`organization_id`	Yes
`evidence_artifact`	No
`capability_version`	Yes
`machine_principal_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds the useful access constraint ('owner-scoped') and a liability disclaimer about modeled sphere validation, which is context beyond the annotations even though it is not operational behavior such as error modes or result availability.

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?

Two short sentences, front-loaded with the operation and scope, with no filler. The second sentence is a domain-appropriate safety caveat that earns its place in a robotics context, though it could be tighter.

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

Completeness3/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 described, and annotations cover safety semantics. What remains missing is the job_id contract and any routing signal distinguishing this from the other cloud-motion read siblings, which is significant in a 23-tool family.

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?

Only one parameter (job_id) exists, and schema description coverage is 0%, so the description does not explain its format, source, or whether it is a cloud motion job id versus a generic job id. The description adds no meaning beyond the bare property name, which is a real gap given zero coverage, but the single-parameter surface keeps it near baseline.

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?

States a specific verb and resource ('Read ... motion result') plus the access scope ('owner-scoped'), so the operation is identifiable. However, it does not differentiate from closely related siblings such as get_cloud_motion_artifact, get_cloud_motion_receipt, or get_cloud_motion_status, leaving the agent to infer which result-shaped read it needs.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite (e.g. job must be in a completed state), and no named alternative for retrieving status, artifact, or receipt. The word 'owner-scoped' implies an access condition but does not tell the agent what to do when that condition fails or which sibling to choose instead.

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

All RQM Robotics Jobs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?