Skip to main content
Glama
rspace-os

RSpace MCP Server

Official
by rspace-os

move_items_to_specific_grid_locations

Position items at exact coordinates within a grid container for precise experimental layouts and protocols.

Instructions

Places items at specific coordinates within a grid container

Usage: Precise positioning for experimental layouts or protocols Coordinates: Each item gets an exact (row, column) position Validation: Ensures equal number of items and positions

Returns: Success status and confirmation of final positions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_container_idYes
item_idsYes
grid_locationsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool that implements the logic to place specific items at exact grid coordinates in an RSpace inventory grid container using the inv_cli client.
    @mcp.tool(tags={"rspace", "inventory", "movement"})
    def move_items_to_specific_grid_locations(
        target_container_id: Union[int, str],
        item_ids: List[str],
        grid_locations: List[GridLocation]
    ) -> dict:
        """
        Places items at specific coordinates within a grid container
        
        Usage: Precise positioning for experimental layouts or protocols
        Coordinates: Each item gets an exact (row, column) position
        Validation: Ensures equal number of items and positions
        
        Returns: Success status and confirmation of final positions
        """
        if len(item_ids) != len(grid_locations):
            raise ValueError("Number of items must match number of grid locations")
        
        locations = [i.GridLocation(loc.x, loc.y) for loc in grid_locations]
        placement = i.ByLocation(locations, *item_ids)
        result = inv_cli.add_items_to_grid_container(target_container_id, placement)
        return {"success": result.is_ok(), "results": result.data if hasattr(result, 'data') else str(result)}
  • main.py:69-73 (schema)
    Pydantic model defining the input schema for grid positions (x: column, y: row, 1-based indexing). Used in the tool's grid_locations parameter.
    class GridLocation(BaseModel):
        """Specific position within a grid container"""
        x: int = Field(description="Column position (1-based)")
        y: int = Field(description="Row position (1-based)")
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses validation behavior ('Ensures equal number of items and positions') and return information ('Success status and confirmation of final positions'), which is helpful. However, it doesn't mention potential side effects like overwriting existing items at coordinates, permission requirements, or error conditions for invalid coordinates.

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?

The description is well-structured with clear sections (purpose, usage, coordinates, validation, returns) in just 4 sentences. Every sentence adds value with no redundant information, making it easy to scan and understand quickly.

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?

Given 3 parameters with 0% schema coverage and no annotations, the description does a good job explaining core functionality. The presence of an output schema means it doesn't need to detail return values. However, for a mutation tool with precise positioning, it could better address potential risks like coordinate conflicts or container constraints.

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 description coverage is 0%, so the description must compensate. It explains the purpose of coordinates ('Each item gets an exact (row, column) position') and validation logic, adding meaningful context beyond the bare schema. However, it doesn't clarify the relationship between item_ids and grid_locations arrays or explain what target_container_id represents.

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?

The description clearly states the tool's purpose with specific verb ('places items') and resource ('at specific coordinates within a grid container'). It distinguishes from sibling tools like 'move_items_to_grid_container_by_column' and 'move_items_to_grid_container_by_row' by emphasizing precise positioning rather than bulk movement by row/column.

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?

The 'Usage' line provides clear context ('Precise positioning for experimental layouts or protocols'), indicating when this tool is appropriate. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, though the distinction from row/column movement tools is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rspace-os/rspace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server