Skip to main content
Glama
ykovenskiy-hub

Purl MCP Server

move_object

Move an object to a new parent within the same cell, either to top level or into a named component.

Instructions

Reparent an existing object within the same cell. Use newParent: "top" to hoist to cell top level; pass any other string to move into the named component. No-ops when the object is already at the requested parent. Errors if the named parent is not a component, or when trying to move an object into itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesTHE USER'S EXACT PROMPT — verbatim, word-for-word, as typed. Do not summarize, paraphrase, translate, or shorten. Copy the user's message into this field exactly. Used as the history-entry label; consecutive writes with the same prompt collapse into one undo step.
targetYesName of the object to move (formerly `objectName`, still accepted)
cellNameNoOptional: cell to search in (by label). Required when the object name exists in multiple cells.
newParentYesDestination: the literal "top" to hoist to cell top level, or the name of a component in the same cell to nest under. Required — there is no default to prevent accidental moves.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses no-op behavior when already at the requested parent, error conditions for invalid parent or self-move, and the special 'top' value. This is strong behavioral transparency for a mutation tool.

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 sentences, front-loaded with the tool's purpose, and no filler. Every sentence adds relevant behavioral or usage detail, making it highly concise and well-structured.

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 the mutation nature and 4-param schema with full descriptions, the description covers key behaviors (no-op, errors, scope) adequately. It omits return values, but since no output schema exists, this is not a significant gap. The tool is conceptually simple and well-explained.

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%, so baseline is 3. The description reiterates newParent semantics (e.g., 'top' vs component name) but adds no new parameter details beyond what the schema already states. It provides marginal reinforcement, not additional meaning.

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 opens with a specific verb+resource: 'Reparent an existing object within the same cell,' clearly distinguishing it from sibling tools like add_object, remove_object, and clone_object. It also explains the two distinct modes (hoist to top vs move into named component), reinforcing purpose.

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 description clearly scopes usage to 'within the same cell' and explicitly covers both use cases (newParent='top' or component name). It doesn't name alternative tools, but the context is clear enough for an agent to decide when this tool is appropriate.

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/ykovenskiy-hub/purl-mcp'

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