Skip to main content
Glama
Sign In
robotarm

robotarm

by walcorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_scene

Retrieves the robot workcell scene: objects at each station, items held by each hand, and whether the cell is stopped. Use it to inspect state before planning moves.

Instructions

Current objects per station, what each hand holds, and whether the cell is stopped.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. The word "current" implies a non-mutating snapshot read, and the description does disclose what the observation contains, but it never explicitly states that the call is read-only, side-effect free, or whether the snapshot is instantaneous or eventually consistent.

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 compact sentence with zero wasted words, front-loading the per-station object state. It is a verbless noun phrase rather than a sentence, which slightly weakens front-loading of intent (observe/read) but keeps the definition tight.

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?

With no annotations and no output schema, the description does the necessary work by naming the three things returned, which is what an agent needs to decide the call is worthwhile. It omits the shape of "objects per station" (identifiers vs. full object records), leaving minor ambiguity for a tool whose output is entirely undocumented elsewhere.

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?

The tool takes zero parameters, so there is no parameter meaning the description could add or omit; the baseline for a parameterless tool applies. Nothing in the schema needs compensating for.

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 enumerates the specific resource contents: objects per station, hand contents, and cell stopped state, which tells an agent exactly what a call returns. It lacks a verb (implicitly a read of current state) and never distinguishes itself from the similar sibling get_workcell, so it stops short of a 5.

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 at all: nothing says to call this before pick/place/move_object to verify state, nor how it relates to get_workcell or recent_actions. The agent must infer that this is the observation primitive for the cell from the name alone.

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

Deploy Server

Other Tools