Skip to main content
Glama
ykovenskiy-hub

Purl MCP Server

remove_value_at_path

Delete a value at a path in a Purl object. Arrays remove the indexed element and shift subsequent ones; maps delete the keyed entry. Errors if the path doesn't exist.

Instructions

Remove a single value at the given path. For arrays, removes the element at the bracket index and shifts subsequent elements down. For maps, deletes the keyed entry. Errors if the path doesn't exist (no silent no-ops).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDotted/bracketed path to the entry to remove (e.g., "value[5]", "value.config.foo").
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 (formerly `objectName`, still accepted)
cellNameNoOptional: cell to search in (by label)
expectedVersionNoOptional precondition: hash of the top-level property (from get_object's `_versions[topSlot]`). When supplied, rejects the call if the top slot has changed since you read it.
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses important behavioral traits: array element shifting, map entry deletion, and error on non-existent path (no silent no-ops). This goes well beyond the schema and provides clear expectations for a mutating operation.

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 two sentences, front-loaded with the main purpose, and every sentence adds value. It is concise without unnecessary detail.

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?

The tool has no output schema or annotations, but the description explains core behavior and error conditions well. However, it omits details about the return value on success and any undo/versioning implications, which would be useful given the mutation context.

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 coverage is 100%, so all parameters are documented in the schema. The description adds minor context about path behavior (e.g., bracket index) but does not significantly enhance parameter semantics beyond what the schema already provides.

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 removes a single value at a given path, with explicit behavior for arrays (shift elements) and maps (delete keyed entry). This distinguishes it from sibling tools like set_value_at_path, which sets rather than removes.

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

Usage Guidelines3/5

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

The description implies the tool is for removing values but does not explicitly mention when to use it over alternatives or provide exclusions. It lacks direct comparison to set_value_at_path or push_value, so usage context is only 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/ykovenskiy-hub/purl-mcp'

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