Skip to main content
Glama

Remove Context Item

remove_context_item

Removes a list item from the project context by zero-based index, using a dot path to target lists such as active_tasks or key_files.

Instructions

Remove an item from a list in the project context by index.

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": {
      "dot_path": "<dot_path>",
      "index": "<index>"
    },
    "name": "remove_context_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
indexYesZero-based index of the item to remove.
dot_pathYesPath to the list (e.g. 'active_tasks', 'key_files').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure for a mutating operation. It never states whether removal is reversible, whether subsequent indices shift, what happens on an out-of-range index, or whether the item must exist — all things an agent needs before calling a destructive tool.

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 front-loaded sentence with no filler, and the scope qualifier ('in the project context') is placed before the mechanism. It is efficient but borders on under-specified rather than merely concise.

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?

The tool is low-complexity with just three parameters, all fully described in the schema, and an output schema exists so return values need no explanation. However, for an unannotated mutation the description says nothing about side effects, index behavior, or failure modes, leaving a noticeable behavioral gap.

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 every parameter (path, index, dot_path) is already documented with meaning and examples in the schema. The description's only added phrase, 'by index', restates what the schema already says, so it neither compensates nor detracts — baseline 3 applies.

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 gives a specific verb-plus-resource ("Remove an item from a list in the project context") and adds the indexing mechanism, which distinguishes it from siblings like add_to_context_list and update_context. It stops short of explicitly naming those counterparts, but the operation is unambiguous.

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 guidance on when to use this versus update_context, add_to_context_list, or reset_context, and no stated prerequisites. The only usage signal is implicit in 'remove ... by index', leaving the agent to infer that the list must already exist and that removal is positional rather than value-based.

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